Update dependency i18next to v26

[renovate]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
i18next (source)	22.0.3 → 26.3.1

---

Release Notes

i18next/i18next (i18next)

v26.3.1

Compare Source

• fix(types): t() with a keyPrefix no longer pollutes its return type with sibling keys' values. A regression in 26.3.0 — the [Res] extends [never] guards added to KeysBuilderWithReturnObjects / KeysBuilderWithoutReturnObjects turned the builders into deferred conditional types, so KeyPrefix<Ns> stopped resolving to a literal union and keyPrefix inference widened to the whole namespace. Symptom: useTranslation(ns, { keyPrefix: 'a.b' }) then t('title') would resolve to '<a.b>.title' | '<other.path>.title' | ... instead of just the scoped value. Affected every react-i18next user using keyPrefix. Restored to the eager 26.2.0 form. The same-namespace conflict handling from #​2434 still works via _DropConflictKeys at the merge layer (in options.d.ts). Thanks @​aaronrosenthal (#​2436).

v26.3.0

Compare Source

• feat(types): introduce ResourceNamespaceMap — a separate mergeable augmentation surface for namespace resource types, designed for monorepos where multiple packages each want to contribute their own namespaces. Previously, every package had to coordinate on a single CustomTypeOptions.resources declaration (or fall back to typing dependency namespaces as any) because resources is a single property of an interface and TypeScript reports TS2717 when two declarations of the same property disagree. The new interface merges naturally across declare module 'i18next' blocks, so each package can ship its own i18next.d.ts independently. Per-property merge handles same-namespace contributions from multiple packages, and same-key/different-literal conflicts are silently dropped to avoid poisoning t() overload resolution. Fully backwards-compatible — existing CustomTypeOptions.resources augmentations continue to work, and both surfaces can coexist. Scalar options (defaultNS, returnNull, enableSelector, etc.) still belong on CustomTypeOptions. Thanks @​sh3xu (#​2434). Fixes #​2409.

v26.2.0

Compare Source

• feat(types): new parseInterpolation TypeOption (default true). When set to false in CustomTypeOptions, the type-level extractor stops parsing translation strings for {{variable}} patterns. Required by i18next-icu users — the default extractor mistakes ICU MessageFormat nested-brace plurals like {count, plural, one {{count} row} other {{count} rows}} for an interpolation block and demands a phantom variable name. The flag is type-only; runtime interpolation is governed by InterpolationOptions and is unaffected. Fixes i18next-icu#85.
• fix(types): expose enableSelector on InitOptions so i18next.init({ enableSelector: 'strict' }) typechecks without a module augmentation. The runtime already reads opts?.enableSelector from init options; this lands the matching type declaration next to the other selector-resolution knobs. Accepts false | true | 'optimize' | 'strict'. Thanks @​Faithfinder (#​2431)

v26.1.0

Compare Source

• feat: enableSelector: 'strict' (TypeOptions + runtime option). Opt-in mode that drops the flattened-primary form from NsResource at the type level — every namespace (primary included) is exposed only under its own key on $, uniformly across single- and multi-ns hooks. At runtime, a leading selector path segment matching the scope's namespace list is always rewritten as a namespace prefix, including the primary. Eliminates the silent-miss surface area where t($ => $.primary.foo) typechecks but doesn't resolve under the default mode (see #​2429). Backward-compatible: default enableSelector: false | true | 'optimize' behavior is unchanged. Note: strict mode is incompatible with the #​2405 pattern (keys whose names match sibling namespaces) — those users should stay on default mode.

v26.0.10

Compare Source

• feat: getFixedT accepts a fourth optional fixedOpts argument carrying scopeNs — the full namespace list the bound t was created for. The selector API uses scopeNs to detect when a path's first segment is a namespace prefix, without changing resolution scope. Resolution still uses the bound ns (a single primary string in the typical react-i18next setup), so plain t('key') lookups stay isolated to the primary namespace exactly as before — only t($ => $.secondaryNs.foo) selectors now route correctly under useTranslation([nsA, nsB]). Fixes the runtime side of #​2429 for the react-i18next default-nsMode case. The 4th argument is opt-in: existing 3-arg getFixedT(lng, ns, keyPrefix) callers see no behavior change.

v26.0.9

Compare Source

• fix(types): unformatted interpolation values are now typed as string | number (was string). i18next stringifies values at runtime, so requiring callers to wrap numbers in String(...) for plain {{var}} placeholders was unnecessary friction — and could mask the real problem when a non-string value was passed alongside multiple interpolation slots (the t() overload resolution would fall through to the 3-arg form and report a confusing "not assignable to string" error against the options object). Typed format specifiers like {{x, number}}, {{x, currency}}, {{x, datetime}}, etc. keep their precise types; this only relaxes the no-format default. The count variable remains number-only

v26.0.8

Compare Source

• fix(types): restore the pre-v25.10.4 ExistsFunction shape so plain arrow functions can again be assigned to ExistsFunction-typed variables (TypeScript cannot infer type predicates through multi-overload assignment). Direct i18next.exists(key) calls still narrow key to SelectorKey — the predicate is now declared inline on i18n.exists. Custom wrappers that want the narrowing can type themselves as typeof i18next.exists 2425

v26.0.7

Compare Source

• fix: when a plural lookup misses, the missingKey debug log now shows the actual plural-resolved key (e.g. foo.bar_many for Polish count: 14) instead of the base key — making it obvious which plural category was expected and missing 2423
• chore: drop @babel/runtime runtime dependency. The build no longer generates any @babel/runtime imports, so the package is unused by consumers. Rollup now uses babelHelpers: 'bundled' so any helpers that are ever needed in the future will be inlined rather than imported externally 2424
• chore: stop emitting dist/esm/i18next.bundled.js. It was byte-identical to dist/esm/i18next.js because no helpers were being imported 2424

v26.0.6

Compare Source

Security release — all issues found via an internal audit.

• security: warn when a translation string combines escapeValue: false with interpolated variables inside a $t(key, { ... "{{var}}" ... }) nesting-options block. In that narrow combination, attacker-controlled string values containing " can break out of the JSON options literal and inject additional nesting options (e.g. redirect lng/ns). The default escapeValue: true configuration is unaffected because HTML-escaping neutralises the quote before JSON.parse. See the security note in the Nesting docs for the full pattern and mitigations
• security: apply regexEscape to unescapePrefix / unescapeSuffix on par with the other interpolation delimiters. Prevents ReDoS (catastrophic-backtracking) when a misconfigured delimiter contains regex metacharacters, and fixes silent breakage of the {{- var}} syntax when the delimiter contains characters like (, [, .
• security: strip CR/LF/NUL and other C0/C1 control characters from string log arguments to prevent log forging via user-controlled translation keys, language codes, namespaces, or interpolation variable names (CWE-117)
• chore: ignore .env* and *.pem/*.key files in .gitignore

v26.0.5

Compare Source

• fix: cloneInstance().changeLanguage() no longer fails to update language state when the target language is not yet loaded — a race between init()'s deferred load() and the user's changeLanguage() could overwrite isLanguageChangingTo, causing setLngProps to be skipped 2422

v26.0.4

Compare Source

• fix(types): inline formatting options like {{price, currency(EUR)}} are now correctly resolved to their base format type (e.g. number for currency) instead of falling back to string 2378

v26.0.3

Compare Source

• fix(types): addResourceBundle now accepts an optional 6th options parameter ({ silent?: boolean; skipCopy?: boolean }) matching the runtime API 2419

v26.0.2

Compare Source

• fix(types): t("key", {} as TOptions) no longer produces a type error — the context constraint now bypasses strict checking when context is unknown (e.g. from TOptions) 2418

v26.0.1

Compare Source

• feat: getFixedT accepts a fourth optional fixedOpts argument carrying scopeNs — the full namespace list the bound t was created for. The selector API uses scopeNs to detect when a path's first segment is a namespace prefix, without changing resolution scope. Resolution still uses the bound ns (a single primary string in the typical react-i18next setup), so plain t('key') lookups stay isolated to the primary namespace exactly as before — only t($ => $.secondaryNs.foo) selectors now route correctly under useTranslation([nsA, nsB]). Fixes the runtime side of #​2429 for the react-i18next default-nsMode case. The 4th argument is opt-in: existing 3-arg getFixedT(lng, ns, keyPrefix) callers see no behavior change.

v26.0.0

Compare Source

This is a major breaking release:

Breaking Changes

• Remove deprecated initImmediate option — the backward-compatibility mapping from initImmediate to initAsync (introduced in v24) has been removed. Use initAsync instead.
• Remove legacy interpolation.format function — the old monolithic format function (interpolation: { format: (value, format, lng) => ... }) is no longer supported. The built-in Formatter (or a custom Formatter module via .use()) is now always used. Migrate to the new formatting approach using i18next.services.formatter.add() or .addCached() for custom formatters.
• Remove console support notice — the console support notice introduced in v25.8.0 has been removed, along with the showSupportNotice option and all related internal suppression logic (globalThis.__i18next_supportNoticeShown, I18NEXT_NO_SUPPORT_NOTICE env var). See our blog post for the full story.
• Remove simplifyPluralSuffix option — this option was unused by the core PluralResolver (which relies entirely on Intl.PluralRules). It only had an effect in the old v1/v2/v3 compatibility layer. The v4 test compatibility layer now defaults to true internally.
• Remove deprecated @babel/polyfill from devDependencies.

Improvements

• Code modernization across all source files:
  • Replace indexOf() > -1 / indexOf() < 0 with .includes() (~40+ occurrences)
  • Replace indexOf() === 0 with .startsWith() where appropriate
  • Replace var with const, '' + object with String(object), .substring() with .slice()
  • Replace .apply(observer, [event, ...args]) with direct call observer(event, ...args)
  • Remove unnecessary .call(this, ...) in BackendConnector retry logic
  • Fix array-callback-return in LanguageUtils getBestMatchFromCodes
  • Clean up all stale eslint-disable comments from source files
• EventEmitter: add once() method for one-time event subscriptions
• Memory leak fix: move module-level checkedLoadedFor cache to Translator instance, preventing cross-instance state leakage
• TypeScript: fix BackendModule generic parameter naming inconsistency between CJS and ESM type definitions
• TypeScript: add once() method to i18n and ResourceStore type interfaces
• ESLint 9: migrate from ESLint 8 (airbnb-base) to ESLint 9 flat config with neostandard
• Vitest 4: upgrade from vitest 3 to vitest 4, migrate workspace files to test.projects config

v25.10.10

Compare Source

• feat: suppress support notice automatically in production environments (NODE_ENV=production)

v25.10.9

Compare Source

• 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

Compare Source

• fix(types): reorder TFunctionSelector overloads so Parameters<TFunction> resolves to the general selector signature instead of the branded SelectorKey type 2412

v25.10.7

Compare Source

• feat(types): support typescript 6 to address i18next/react-i18next#1910

v25.10.6

Compare Source

• feat(types): support typescript 6 to address i18next/react-i18next#1910

v25.10.5

Compare Source

• 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

Compare Source

• 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

Compare Source

• check also for I18NEXT_NO_SUPPORT_NOTICE env variable

v25.10.2

Compare Source

• 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

Compare Source

• feat: suppress support notice automatically in production environments (NODE_ENV=production)

v25.10.0

Compare Source

• 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

Compare Source

• 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

Compare Source

• fix: getFixedT() selector now resolves namespaces against the effective ns rather than the global init options 2406

v25.8.19

Compare Source

• 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

Compare Source

• improve selector api to accept array of selector functions, analogous to array of keys 2404

v25.8.17

Compare Source

• update deps

v25.8.16

Compare Source

• 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

Compare Source

• fix: Selector API unable to resolve namespaces 2402

v25.8.14

Compare Source

• fix: getCleanedCode now replaces all underscores

v25.8.13

Compare Source

• improve support notice shown logic

v25.8.12

Compare Source

• improve support notice shown logic

v25.8.11

Compare Source

• revert fix: compatibility with moduleResolution bundler (issue 2380) 2381

v25.8.10

Compare Source

• fix(interpolator): guard null matchedDoubleQuotes in nesting option parsing 2395

v25.8.9

Compare Source

• fix(interpolator): escape nestingOptionsSeparator in nesting option parsing 2394

v25.8.8

Compare Source

• types(i18n): add missing toJSON() declaration 2393

v25.8.7

Compare Source

• avoid crash due to ReferenceError without Intl API 2391

v25.8.6

Compare Source

• ts: address incomplete type definition for getFixedT() return value 2318

v25.8.5

Compare Source

• fix: compatibility with moduleResolution bundler (issue 2380) 2381

v25.8.4

Compare Source

• fix: crashes when backend in backends array has no name property 2386

v25.8.3

Compare Source

• ts: document option to suppress the support message 2385

v25.8.2

Compare Source

• fix: getFixedT() selector now resolves namespaces against the effective ns rather than the global init options 2406

v25.8.1

Compare Source

• 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.0

Compare Source

• fix: TFunctionReturn fallback 2360
• chore: added a console.info support notice regarding the open-source sustainability of the i18next ecosystem. (Note: This can be easily suppressed via showSupportNotice: false, globalThis, or environment variables. See the FAQ for details on how to disable it).

v25.7.4

Compare Source

• fix: Interpolation breaks when cloning an instance 2376

v25.7.3

Compare Source

• type definitions for new transDefaultProps option in react-i18next react-i18next: #​1895

v25.7.2

Compare Source

• fix: Invalid overwrite of default value for overloadTranslationOptionHandler 2374.

v25.7.1

Compare Source

• TS: remove wrong signature 2372.

v25.7.0

Compare Source

• Enhance cloneInstance to create a new interpolator if interpolation options are passed in. This will address 2371.

v25.6.3

Compare Source

• chore: dependency updates 2368

v25.6.2

Compare Source

• types: export InterpolationMap

v25.6.1

Compare Source

• fix: createInstance does not exist on an instance 2366

v25.6.0

Compare Source

• feat: exists() method now respects returnObjects option - returns false when accessing an object key with returnObjects: false, enabling detection of object vs string keys 2359

  Note: This is a potential behavior change. If you were previously calling exists() with returnObjects: false on object keys, those calls will now return false instead of true. This enables developers to detect whether a key points to an object or string value.

v25.5.3

Compare Source

• export esm type declaration for keyFromSelector 2356

v25.5.2

Compare Source

• fix last change => for cjs there is just 1 default export, no named exports, fixes 2348

v25.5.1

Compare Source

• export keyFromSelector from index.cjs 2347

v25.5.0

Compare Source

• export keyFromSelector function for testing purposes 2346

v25.4.2

Compare Source

• fix: enableSelector: true doesn't work with custom keySeparator 2341

v25.4.1

Compare Source

• fix: KeyPrefix not working with new selector api 2340

v25.4.0

Compare Source

• add new selector API to improve TypeScript IDE performance 2322
  • To enable it, set enableSelector: true in your configuration options
  • With enableSelector: "optimize", i18next can now handle translation dictionaries of any size, without affecting IDE performance or build times
  • To assist with the migration, we've published the following packages:
    • @​i18next-selector/codemod
    • @​i18next-selector/vite-plugin

v25.3.6

Compare Source

• improve fix: Ordinals and non-ordinals don't work together 2337

v25.3.5

Compare Source

• fix: Ordinals and non-ordinals don't work together 2337

v25.3.4

Compare Source

• remove unnecessary debug logs

v25.3.3

Compare Source

• fix: Brackets breaking nesting interpolation 2336

v25.3.2

Compare Source

• fix dir() for non-Intl language codes 2330

v25.3.1

Compare Source

• warn if legacy interpolation.format function is still used

v25.3.0

Compare Source

• feat: support formatting function with plural and interpolation 2325
• fix dir() for Latn language codes 2324

v25.2.1

Compare Source

• streamline fallbackLng option of t call with the init options 2312

v25.2.0

Compare Source

• introduce cacheInBuiltFormats option to address 2227

v25.1.3

Compare Source

• Ensure nsSeparator is respected when appendNamespaceToMissingKey is true 2311, fixes 2310

v25.1.2

Compare Source

• do not mutate t options, fixes 2307

v25.1.1

Compare Source

• fix options type for parseMissingKeyHandler

v25.1.0

Compare Source

• feat: parseMissingKeyHandler now takes options as parameter like in missingKeyHandler 2304

v25.0.2

Compare Source

• fix cloneInstance with forkResourceStore: true addresses 2303

v25.0.1

Compare Source

• optimize changeLanguage to correctly use getBestMatchFromCodes (string or array) 2299 and improve resolvedLanguage set for non canonical codes

v25.0.0

Compare Source

This is a potentially breaking release:

• fix multiple changeLanguage call that may have result in wrong order in previous versions 1605 2298
• adapt changeLanguage to always (string or array) use getBestMatchFromCodes 2299
• getBestMatchFromCodes now tries to fallback to language code with same script 2299

v24.2.3

Compare Source

• Upgrade @​babel/runtime package to version v7.26.10 2293

v24.2.2

Compare Source

• fix: Interpolation fails with arrays (TypeError) and doesn't work with objects in defaultValue 1829

v24.2.1

Compare Source

• Standardize null/undefined checks across codebase 2275
• fix(typescript): make TFunction augmentable again 2279, fixes 2278

v24.2.0

Compare Source

• feat(typescript): Add strictKeyChecks option to enforce checking key existence when defaultValue is used 2274, fixes 2043

v24.1.2

Compare Source

• optimize fix: Bug Report: Unsafe Behavior in i18n.t Function Leading to Potential Code Execution 2273

v24.1.1

Compare Source

• fix: Bug Report: Unsafe Behavior in i18n.t Function Leading to Potential Code Execution 2273

v24.1.0

Compare Source

• try to address 2270 by cloning the store data 2271

v24.0.5

Compare Source

• remove extra log for 2268

v24.0.4

Compare Source

• simplify fix: incorrect locale detected 2268

v24.0.3

Compare Source

• fix: incorrect locale detected 2268
• fix: Intl.getCanonicalLocales throws with custom regions 2267

v24.0.2

Compare Source

• if no Intl api, log error and use dummy rule

v24.0.1

Compare Source

• early return and log error, if no Intl api

v24.0.0

Compare Source

This is a major breaking release:

• remove support for older environments
• remove old i18next JSON formats
  • To convert your existing v3 translations to the v4 format, have a look at i18next-v4-format-converter or this web tool.
• remove support for compatibility to v1 API
• Intl API is mandatory now and will not fallback anymore
• possible compatibility layer for older formats: test/compatibility/v4/v4Compatibility.js
• rename initImmediate to initAsync
• fallback to dev language if plural rule not found
• Dropped support for Node.js < v14
• remove TypeScript v4 support. TypeScript v5 is now an optional peer dependency
• addresses
  • 2244
  • 2184
  • 2213
  • 2206
  • 2208
  • 2148
  • 2254

➡️ check out the migration guide

v23.16.8

Compare Source

• fix(plural): Create cache entry for PluralRules created as part of the fallback flow 2256

v23.16.7

Compare Source

• if plural rule is not found, try to search with language only code 2252

v23.16.6

Compare Source

• fix: Small typo in the type definitions 2250

v23.16.5

Compare Source

• fix extractFromKey for use cases like this

v23.16.4

Compare Source

• revert formatter change 2247 because of caching not working anymore

v23.16.3

Compare Source

• fix utils imports for Deno

v23.16.2

Compare Source

• perf(size): Adds a isString utility 2248

v23.16.1

Compare Source

• perf: Optimize size of Formatter 2247

v23.16.0

Compare Source

• use Intl.getCanonicalLocales function if available to format language code, like suggested in 2244

v23.15.2

Compare Source

• fix(types): make context related keys detection stricter 2243 fixes 2242

v23.15.1

Compare Source

• types(TFunction): make return not inferrable and use defaultValue as return when provided 2234

v23.15.0

Compare Source

• support unescaped variables in TypeScript 2233

v23.14.0

Compare Source

• If backend errors with retry flag, set internal state to 0, so reloadingResources should work 147

v23.13.0

Compare Source

• Cache output of getRule to optimize performance 2226

v23.12.7

Compare Source

• revert last optimization to address 2227

v23.12.6

Compare Source

• remove console.log statement 2227

v23.12.5

Compare Source

• try to optimize last fix for 2227

v23.12.4

Compare Source

• try to address 2227 without the removal of cached formatter for in-built formatters

v23.12.3

Compare Source

• fix: Using a comma in a formatter parameter 2225

v23.12.2

Compare Source

• fix: Nested translation resolution between languages uses the fallback language for nested translations 2216 by preserving issue fix "lng is undefined when formatter used in $t( )" 1938

v23.12.1

Compare Source

• Use explicit imports for utils 2212

v23.12.0

Compare Source

• feat: Add posibility to override keyPrefix for certain translation. 2211

v23.11.5

Compare Source

• perf: use Array.isArray() 2193
• perf: trim keys once 2194

v23.11.4

Compare Source

• perf(interpolator): use object deconstruction 2181

v23.11.3

Compare Source

• fix: Unsupported language is automatically added to preload option 2178

v23.11.2

Compare Source

• allow defaultValue in nested translation 2174

v23.11.1

Compare Source

• types: remove const from ParseKeys Context type parameter and disable skipLibCheck 2169

v23.11.0

Compare Source

• Fix typing performance regression 2166

v23.10.1

Compare Source

• optimize getBestMatchFromCodes for i18next/i18next-browser-languageDetector#281

v23.10.0

Compare Source

• Add 'isInitializing' property so we're able to detect init() was already called 2141

v23.9.0

Compare Source

• types: support nested keys in InterpolationMap 2140 fixes 2014

v23.8.3

Compare Source

• prevent resource mutation when using addResourceBundle 2081

v23.8.2

Compare Source

• optimize addResources to address 2130

v23.8.1

Compare Source

• types: support stricter typechecking for returnEmptyString and returnNull 2129

v23.8.0

Compare Source

• improve performance by reducing array slices and RegExp recreation 2128

v23.7.20

Compare Source

• optimize: consistent _zero special handling also

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
  • Only on Sunday and Saturday (* * * * 0,6)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.