Sourced from react-i18next's changelog.
17.0.10
- fix(warnings): the
useTranslationandTrans"You will need to pass in an i18next instance" warnings now match theuseSSRwording, mentioning the props/context alternatives and the most common unexplained cause at scale: duplicate react-i18next copies in monorepo setups. TheTransvariant also referenced the internali18nextReactModulename; it now points to the publicinitReactI18nextAPI.- feat(warnings): development-only warning (
SUSPENDED_WHILE_LOADING, logged once) right beforeuseTranslationsuspends while translations are loading. With the defaultuseSuspense: trueand no<Suspense>boundary this previously surfaced as a blank screen or a cryptic React error; the warning now names both fixes (add a<Suspense>boundary or setreact.useSuspense: false). No-op in production builds; theprocess.env.NODE_ENVcheck is wrapped so runtimes without aprocessglobal (raw ESM in the browser, some edge runtimes) stay silent instead of throwing.- ci: weekly workflow typechecking the test suite against
@types/react@next/@types/react-dom@next, so the next React major's type changes (like the React 18TFunctionResult/children wave) surface before user reports.
3b71c27
17.0.1057c3500
buildc62476f
chore: sync package-lock with i18next ^26.2.0 devDependency bump0126bd1
improve instance warnings (monorepo hint) + dev-only suspense warning +
weekl...