Skip to content

chore(web): bump i18next to 27.1.0 and react-i18next to 18.0.1 - #1436

Merged
mforce merged 2 commits into
mainfrom
chore/i18next-27-react-i18next-18
Nov 14, 2026
Merged

mforce merged 2 commits into
mainfrom
chore/i18next-27-react-i18next-18

Conversation

@mforce

@mforce mforce commented Nov 14, 2026

Copy link
Copy Markdown
Owner

Supersedes #1425 and #1427, which cannot carry the code change this bump needs.

What and why

  • i18next 26.7.1 → 27.1.0 and react-i18next 17.1.11 → 18.0.1. react-i18next 18 peer-requires i18next ≥ 27, so the two only work as one change — hence a single PR rather than the two Dependabot PRs.
  • The one code change: NavLabelKey is now ParseKeysWithoutVariables<"nav"> instead of keyof Resources["nav"]. i18next 27 turns strictInterpolationChecks on by default, which refuses keys with required interpolation variables from a no-options t() — including inside a union. nav's one such key is versionLabel ("v{{version}}"), which AppLayout passes with its variable directly; it never rides the nav model. All 7 TS2345 errors (BottomNav ×3, AppLayout ×3, HelpPage ×1) collapse to this one type.

Docs-impact: none — dependency bump plus a type narrowing; no user-visible strings or help content change.

Verification

  • npm run typecheck — 0 errors
  • npm run test — 183 files, 4425 tests passed
  • npm run lint
  • npm run build

@mforce
mforce merged commit b51bd4b into main Nov 14, 2026
21 checks passed
@mforce
mforce deleted the chore/i18next-27-react-i18next-18 branch November 14, 2026 05:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant