Internationalization for react done right. Using the i18next i18n ecosystem.
Stars
9.9k
Forks
1.1k
Watchers
9.9k
Open Issues
0
Overall repository health assessment
^7.29.2^3.0.1^1.6.0^7.28.6^7.29.0^7.28.6^7.20.7^7.20.7^7.28.6^7.29.0^7.12.1^7.29.2^7.28.5^7.28.6^7.0.0^29.0.2^16.0.3^6.0.31.0.0^10.4.1^6.9.1^16.3.2^30.0.0^19.2.14^4.1.2^6.26.1^7.0.0-bridge.0^3.1.0^11.0.4^3.1.1^7.0.0^10.1.0^8.57.019.0.4^9.1.0^2.32.0^5.5.0^6.10.2^7.37.5^6.5.0^20.8.9^9.1.7^26.0.3^16.4.0^3.0.1^3.8.1^19.2.4^19.2.4^19.2.4^6.1.3^4.60.0~6.0.2^4.1.2^18.0.0>= 26.0.1>= 16.8.0^5 || ^6859
commits
524
commits
41
commits
32
commits
26
commits
24
commits
22
commits
19
commits
16
commits
12
commits
fix(types): `values` prop on `<Trans />` now only requires interpolation variables for the specific `i18nKey`, not all variables in the namespace #1913
61fe80cView on GitHubl10n: add Swedish language support to examples (#1912)
b58d5a5View on GitHubfix: `transKeepBasicHtmlNodesFor` now correctly preserves HTML tag names when children contain interpolations or mixed content
f4ada4cView on GitHubfix(peer-deps): bump i18next peer dependency to `>= 25.10.9` to match required type exports (`ConstrainTarget`, `ApplyTarget`, `GetSource`) used by `TransSelector` #1911
76f98cdView on GitHubfix(types): selector keyPrefix overload in `useTranslation` no longer matches when `keyPrefix` is absent, fixing `defaultNS: false` with explicit `ns` option https://github.com/i18next/i18next/issues/2412
9f0005fView on GitHub