Fix i18n singleton split caused by TypeScript peer dep duplication
Mobile's TypeScript 6 devDep created a second peer-resolution variant of i18next (i18next(typescript@6)) alongside the web apps' (i18next(typescript@5)). Under pnpm's hoisted nodeLinker the server and client ended up with different instances of the i18n singleton, so SSR rendered raw keys and hydration mismatched. Pin i18next and react-i18next TypeScript peer deps to 5.9.3 in root overrides so the entire workspace resolves a single i18next instance regardless of which app's TypeScript version is active. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
c3509b064a
commit
7cf554f85a
2 changed files with 354 additions and 40 deletions
|
|
@ -35,7 +35,9 @@
|
|||
"path-to-regexp@<0.1.13": "0.1.13",
|
||||
"lodash@<4.18.1": "4.18.1",
|
||||
"react": "catalog:",
|
||||
"react-dom": "catalog:"
|
||||
"react-dom": "catalog:",
|
||||
"i18next>typescript": "5.9.3",
|
||||
"react-i18next>typescript": "5.9.3"
|
||||
},
|
||||
"onlyBuiltDependencies": [
|
||||
"@sentry/cli",
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue