Update dependency react-i18next to v16

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-i18next	^14.1.2 → ^16.0.0

---

Release Notes

i18next/react-i18next (react-i18next)

v16.5.0

Compare Source

• Add configuration option transDefaultProps to set default props for the Trans component (e.g. tOptions, shouldUnescape, values) 1895

v16.4.1

Compare Source

• fix(Trans): prevent double-escaping of interpolated values in component props (e.g. title). Unescape HTML entities before passing prop values to React to avoid rendered output like " / &#​39;. #​1893

v16.4.0

Compare Source

• <Trans count> prop: optional - infer count from children 1891

v16.3.5

Compare Source

• fix runaway effect in useTranslation 1888 by 1889

v16.3.4

Compare Source

• Fix: avoid the "ref is not a prop" warning when a user ref is placed on an element inside <Trans> 1887, by still trying to fix element.ref access issue with react 19 1846

v16.3.3

Compare Source

• improve useTranslation to fix "Maximum update depth exceeded" but still support new react-compiler 1885 1863

v16.3.2

Compare Source

• fix: avoid "Uncaught TypeError: Cannot redefine property: __original"

v16.3.1

Compare Source

• revert fix: Incosistent behaviour of Trans and t. Trans set defaultValue when t call doesn't set the field. 1876 f22d478

v16.3.0

Compare Source

• fix: add i18n wrapper for React Compiler and React.memo compatibility 1884

v16.2.4

Compare Source

• try to fix "Trans component do not render anymore children as default value in test environment" 1883 by also respecting 1876

v16.2.3

Compare Source

• fix hyphened component break issue 1882

v16.2.2

Compare Source

• fix trans component break with less than sign 1880, closes 1734

v16.2.1

Compare Source

• fix regression in v16.2.0: bindI18nStore does not work correctly 1879

v16.2.0

Compare Source

• try to address: useTranslation hook violates React's rules of hooks by conditionally calling inner hooks 1863

v16.1.6

Compare Source

• fix: fix: handle spread props for inner components in Trans (icu) 1877

v16.1.5

Compare Source

• fix: Incosistent behaviour of Trans and t. Trans set defaultValue when t call doesn't set the field. 1876
• Trans: use also defaultValue via tOptions as fallback

v16.1.4

Compare Source

• fix: detect pre-transformation use of interpolation like number/date/etc. 1875

v16.1.3

Compare Source

• fix: ensure invalid identifiers are quoted in the props object 1874

v16.1.2

Compare Source

• missing.js extensions for Icu imports

v16.1.1

Compare Source

• exports for IcuTrans component 1873

v16.1.0

Compare Source

• Introduce IcuTrans component 1869

v16.0.1

Compare Source

• fix: Using component with named tags throws error when Selector API is enabled 1867 with 1868

v16.0.0

Compare Source

• major upgrade i18next dep to address 1865

v15.7.4

Compare Source

• downgrade i18next dep to address 1865

v15.7.3

Compare Source

• exports TransSelectorProps 1862 to address 1861

v15.7.2

Compare Source

• update i18next dependency

v15.7.1

Compare Source

• Fix: _EnableSelector type (for compatibility, enableSelector does not exist in TypeOptions) 1858

v15.7.0

Compare Source

• add new selector API to improve TypeScript IDE performance 1852
  • read more about it here

v15.6.1

Compare Source

avoid exception when passing bindI18n: false 1856

v15.6.0

Compare Source

fix: passing components as object should still allow for indexed matching of children 1854

v15.5.3

Compare Source

chore: update @babel/runtime 1851

v15.5.2

Compare Source

fix element.ref access issue with react 19 1846

v15.5.1

Compare Source

add typescript as optional peer dependency 1843

v15.5.0

Compare Source

feat: use const type parameters for useTranslation() 1842

v15.4.1

Compare Source

fix: unique key warning on componentized element 1835

v15.4.0

Compare Source

feat: add meta with codes on warnings to allow conditional logging 1826

v15.3.0

Compare Source

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

v15.2.0

Compare Source

This version may be breaking if you still use React < v18 with TypeScript.
For JS users this version is equal to v15.1.4

• fix: Global JSX namespace is deprecated 1823 with 1822

v15.1.4

Compare Source

• Fix: warning each child should have a unique key 1820

v15.1.3

Compare Source

• fix: Self-closing REACT components in translation strings should not attempt to replace the component's children 1815 1816

v15.1.2

Compare Source

• fix: Attempted to assign to readonly property 1813

v15.1.1

Compare Source

• fix: Not all namespaces are loaded when passing the lng option to useTranslate 1809

v15.1.0

Compare Source

• fix: <Trans /> warns 'Each child in a list should have a unique "key" prop.' for react 19 1806

v15.0.3

Compare Source

• try to fix unexpected token issue

v15.0.2

Compare Source

• try to fix Trans handling with alwaysFormat set to true 1801

v15.0.1

Compare Source

• revert arrow function in class property to address this

v15.0.0

Compare Source

• use optional chaining, nullish coalescing and nullish coalescing assignment 1774
• Build config and optimizations 1769
• some dependency updates 1768
• use modern hasLoadedNamespace code (now requires at least i18next > v19.4.5 (introduced in june 2020))

---

Configuration

📅 Schedule: Branch creation - "on sunday before 6:00am" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[lobehubbot]

👍 @renovate[bot]

Thank you for raising your pull request and contributing to our Community
Please make sure you have followed our contributing guidelines. We will review it as soon as possible.
If you encounter any problems, please feel free to connect with us.
非常感谢您提出拉取请求并为我们的社区做出贡献，请确保您已经遵循了我们的贡献指南，我们会尽快审查它。
如果您遇到任何问题，请随时与我们联系。