Details
-
Bug
-
Resolution: Fixed
-
Major
-
18.2.0-rc-1
-
None
-
Unknown
-
N/A
-
N/A
-
Description
i18next/i18next (i18next)
v25.10.10
- feat: suppress support notice automatically in production environments (NODE_ENV=production)
v25.10.9
- feat(types): export SelectorParam<Ns, KPrefix> helper type — a stable, readable alternative to Parameters<TFunction<Ns>>[0] for typing selector function props 2414
v25.10.8
- fix(types): reorder TFunctionSelector overloads so Parameters<TFunction> resolves to the general selector signature instead of the branded SelectorKey type 2412
v25.10.7
- feat(types): support typescript 6 to address i18next/react-i18next#1910
v25.10.6
- feat(types): support typescript 6 to address i18next/react-i18next#1910
v25.10.5
- feat(types): selector functions as keyPrefix in getFixedT now provide full type-safe key narrowing — the returned t function is scoped to the prefix subtree 2367
v25.10.4
- feat(types): exists() is now a type guard that narrows the key to SelectorKey, so a validated key can be passed directly to t() 2364
v25.10.3
- check also for I18NEXT_NO_SUPPORT_NOTICE env variable
v25.10.2
- feat(types): keyFromSelector is now type-safe — the selector callback is constrained against your resource definitions, catching invalid keys at compile time. Supports optional ns and keyPrefix options for non-default namespace/prefix contexts 2364
v25.10.1
- fix(types): FilterKeys now correctly excludes base keys that have context variants when the provided context doesn't match any of them (e.g. key some with variant some_me is no longer accessible with context="one")
v25.10.0
- feat(types): keyFromSelector now returns a branded SelectorKey type that t() accepts directly, enabling pre-computed and reusable translation keys 2364
- feat: support selector syntax for keyPrefix in getFixedT and per-call options 2367
- feat(types): interpolation values are now automatically typed based on built-in format specifiers — {{val, number}} requires number, {{val, datetime}} requires Date, {{name}} requires string, etc. Custom formatters can be typed via interpolationFormatTypeMap in CustomTypeOptions 2378
- fix(types): FilterKeys in selector mode now preserves non-context, non-plural leaf keys when context is provided, fixing incorrect type narrowing when combining returnObjects: true with context 2398
v25.9.0
- feat(types): selector API now enforces {{
{ count: number }
}} when a key resolves to plural forms 2373
- fix(types): string unions with invalid members are now correctly detected as type errors when used as context option 2172
v25.8.20
-
- fix: getFixedT() selector now resolves namespaces against the effective ns rather than the global init options #2406
v25.8.19
- fix: selector API namespace resolution regression for single-string ns and primary namespace in array #2405. Reverts the broad namespace-prefix rewrite from v25.8.15 and replaces it with a targeted fix that only rewrites paths starting with a secondary namespace in a multi-namespace array, matching the type-level contract of GetSource
v25.8.18
- improve selector api to accept array of selector functions, analogous to array of keys 2404
v25.8.17
- update deps
v25.8.16
- fix(types): on() method now correctly returns this instead of void, matching the runtime behavior and enabling proper method chaining in TypeScript
v25.8.15
- fix: Selector API unable to resolve namespaces #2402
v25.8.14
- fix: getCleanedCode now replaces all underscores
reacti-i18next
v16.6.6
- fix(peer-deps): bump i18next peer dependency to >= 25.10.9 to match required type exports (ConstrainTarget, ApplyTarget, GetSource) used by TransSelector 1911
v16.6.5
- fix(types): selector keyPrefix overload in useTranslation no longer matches when keyPrefix is absent, fixing defaultNS: false with explicit ns option 2412
v16.6.4
- allow TypeScript 6 as peer dependency 1910
v16.6.3
- fix(types): merge TransSelector overloads into a single signature so typeof Trans remains extendable 1909
v16.6.2
- feat(types): useTranslation now accepts selector functions as keyPrefix with full type-safe key narrowing when enableSelector is enabled 2367
v16.6.1
- feat(types): i18nKey of <Trans i18nKey={sk} /> to accept a SelectorKey 2364
v16.6.0
- warn when t is called before ready with useSuspense: false 1896
- type-safe values prop on <Trans /> component — interpolation variables are now inferred from the translation string when custom types are configured 1772
v16.5.8
- A selector function cannot be resolved without an i18n instance... returning empty string is safer than leaking the raw function reference. 1907
v16.5.7
- fix: <Trans> component with enableSelector: true does not support multiple selectors for fallbacks 1907
v16.5.6
- fix: prevent crash in useSSR when init() hasn't been called before useSSR — now logs a warning instead of throwing 1604
v16.5.5
- fix: prevent crash in useSSR, getInitialProps and Translation when no i18next instance is available (e.g. in monorepo setups with duplicate react-i18next copies) — now logs a clear warning instead of throwing 1604