NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #2832 most downloaded on npm
Internationalization for react done right. Using the i18next i18n ecosystem.
Last release 4 days ago
13 Sep 2026
Release timing varies
gaps range from 9 days to 2 months
Most releases are documented
notes for 45 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
387 releases · first in 2015
chore: update @babel/runtime 1851
chore: update @babel/runtime 1851
fix element.ref access issue with react 19 1846
fix element.ref access issue with react 19 1846
One column per quarter.
add typescript as optional peer dependency 1843
add typescript as optional peer dependency 1843
feat: use const type parameters for useTranslation() 1842
feat: use const type parameters for useTranslation() 1842
fix: unique key warning on componentized element 1835
fix: unique key warning on componentized element 1835
feat: add meta with codes on warnings to allow conditional logging 1826
feat: add meta with codes on warnings to allow conditional logging 1826
Uses the i18next logger instead of the default console logger, if there is a valid i18next instance. Now the debug i18next option is respected, and yo
Uses the i18next logger instead of the default console logger, if there is a valid i18next instance. Now the debug i18next option is respected, and you can also inject your own logger module: https://www.i18next.com/misc/creating-own-plugins#logger
fix: Global JSX namespace is deprecated 1823 with 1822
Fix: warning each child should have a unique key 1820
fix: Self-closing REACT components in translation strings should not attempt to replace the component's children 1815 1816
fix: Attempted to assign to readonly property 1813
fix: Not all namespaces are loaded when passing the lng option to useTranslate 1809
fix: warns 'Each child in a list should have a unique "key" prop.' for react 19 1806
<Trans /> warns 'Each child in a list should have a unique "key" prop.' for react 19 1806try to fix unexpected token issue
try to fix Trans handling with alwaysFormat set to true 1801
revert arrow function in class property to address this
use optional chaining, nullish coalescing and nullish coalescing assignment 1774
create a isObject helper function 1766
bring back internal interpolationOverride handling for Trans component (if there are childrens), fixes 1754
do not modify passed tOptions context property to address 1745
types(Trans): add typechecking on context prop 1732 (might break if using "internal" Trans or TransProps)
Trans): add typechecking on context prop 1732 (might break if using "internal" Trans or TransProps)fix: issue 1728 when useSuspense is false and default ns 1731
try to get rid of internal interpolationOverride handling for Trans component, fixes 1729
align context handling of Trans component with t function, fixes 1729
Fix 1691 for strict mode, by preserving change language binding 1720
fix interpolation of the count prop 1719
revert changes done in v14.0.2 since it breaks normal language change render updates
Fix/bug 1691 make returned t function identical upon second effect run in strict mode 1716
types: fix typo in CustomInstanceExtensions 1713
CustomInstanceExtensions 1713types: reportNamespaces is now optional, should fix 1693
self-closing components in translation strings should not attempt to replace the component's children 1695
types: use CustomInstanceExtenstions to extend reportNamespaces
fix: separate cjs and mjs typings
types: fix consider importing '\*.js'
optimize defaultVariables feature introduced in last release
Respect defaultVariables in the interpolation options 1685
Fix missing TransWithoutContext type 1672
types: Allow iterable ReactI18NextChildren as children 1669
Don't use defaults prop as default key 1664
postpone usage of newer ES syntax
Render all children regardless of type when using i18nIsDynamicList prop 1661
Fix non-list dynamic content in Trans component 1660
fix unescape is not consistently called for all values 1657
- export icu.macro 1652
types: Fix performance issue in Trans component 1646
Update types to support t function redesign 1615
optimization for optional lng prop for useTranslation, should now prevent missings when lazy loading translations 1637
optional lng prop for useTranslation (helping on server side 1637)
try to fix conditional exports in package.json
type fix: the type of defaultNS in I18nextProvider should support string[] 1633
if defaultValue is passed in not ready t functio (via useTranslation) return that instead of the key, even though the user-land could should be fixed
fix react merged types 1606 originally introduced with #1531 to address #1506
- fix crash in gatsby 1594
fix fallback of t function in Trans component
- fix crash in gatsby 1594
- fix for node resolution 1589
context-less version of Trans component to be used for environments without react context 1588
Update t function types to rely on types coming from i18next 1501
- types: nsMode 1554
support unescaping forward slash 1548
Your coding agent can read these notes before it upgrades. Set up the MCP server →