Bump react-i18next from 15.6.0 to 16.5.1 in /js

[dependabot]

Bumps react-i18next from 15.6.0 to 16.5.1.

Changelog

Sourced from react-i18next's changelog.

16.5.1

• fix: export nodesToString (runtime + TypeScript typings) to support i18next-cli (i18next/i18next-cli#155)

16.5.0

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

16.4.1

• 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](https://github.com/i18next/react-i18next/issues/39);. 1893

16.4.0

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

16.3.5

• fix runaway effect in useTranslation 1888 by 1889

16.3.4

• 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

16.3.3

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

16.3.2

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

16.3.1

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

16.3.0

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

16.2.4

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

16.2.3

• fix hyphened component break issue 1882

16.2.2

... (truncated)

Commits

• a33d985 16.5.1
• 106eeb7 export nodesToString
• 0ee8a63 16.5.0
• be99228 Add configuration option to set default props for the Trans component #1895
• 09b9d86 16.4.1
• ba059b4 prevent double-escaping of interpolated values #16.4.1
• 7917079 fallback for unescape function
• 2282982 16.4.0
• 31f0d2e \<Trans count> prop: optional - infer count from children #1891
• ba89d1d cosmetics
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: area/dependencies, team/ui. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[augment-app-staging]

🤖 Augment PR Summary

Summary: This PR upgrades the JS UI workspaces to use a newer react-i18next release.

Changes:

• Bumped react-i18next from ^15.6.0 to ^16.5.1 in js/apps/account-ui, js/apps/admin-ui, and js/libs/ui-shared
• Updated js/pnpm-lock.yaml to lock react-i18next@16.5.1 and related transitive dependencies
• Introduced/updated transitive deps pulled in by the bump (e.g. use-sync-external-store, @babel/runtime)
• Lockfile also refreshes some build/tooling-related packages (e.g. esbuild, get-tsconfig) as part of the resolution

Technical Notes: react-i18next@16.5.1 declares a higher i18next peer requirement (>= 25.6.2); it’s worth ensuring the repo’s i18next version satisfies this to avoid peer warnings or install failures.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augment-app-staging]

Review completed. 1 suggestions posted.

Comment augment review to trigger a new review at any time.

[augment-app-staging]

react-i18next@16.5.1 declares a peer requirement of i18next >= 25.6.2, but the lockfile is resolving it against i18next@25.3.2 here; depending on pnpm/CI peer-dep strictness this can warn or fail installs. Consider aligning the i18next version range so it satisfies react-i18next’s peer constraint.

Other Locations

• js/pnpm-lock.yaml:215
• js/pnpm-lock.yaml:403

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[dependabot]

Superseded by #144.