Bump the production-dependencies group across 1 directory with 16 updates

[dependabot]

Bumps the production-dependencies group with 16 updates in the / directory:

Package	From	To
@react-navigation/bottom-tabs	7.15.11	7.18.2
@react-navigation/native	7.2.2	7.3.3
@react-navigation/native-stack	7.14.12	7.17.5
@reduxjs/toolkit	2.11.2	2.12.0
@shopify/flash-list	2.3.1	2.3.2
fuse.js	7.3.0	7.4.2
i18next	26.0.8	26.3.1
react-i18next	17.0.6	17.0.8
react-native-charts-wrapper	0.6.0	0.7.0
react-native-paper	5.15.1	5.15.3
react-native-paper-dates	0.23.6	0.23.9
react-native-safe-area-context	5.7.0	5.8.0
react-native-screens	4.24.0	4.25.2
react-native-svg	15.15.4	15.15.5
react-redux	9.2.0	9.3.0
styled-components	6.4.1	6.4.2

Updates @react-navigation/bottom-tabs from 7.15.11 to 7.18.2

Release notes

Sourced from @​react-navigation/bottom-tabs's releases.

@​react-navigation/bottom-tabs@​7.18.0

7.18.0 (2026-06-11)

Features

• deprecate navigate object overload (66b5164) - by @​satya164

@​react-navigation/bottom-tabs@​7.17.0

7.17.0 (2026-06-07)

Bug Fixes

• flash while switching native bottom tabs with lazy (#13133) (0ae1adb), closes #13132 - by @​dylancom

Features

• add createXScreen helpers to navigators (8b7c2d7) - by @​satya164

@​react-navigation/bottom-tabs@​7.16.2

7.16.2 (2026-05-25)

Bug Fixes

• default lazy to true for native tabs to avoid flicker (ca4ac56) - by @​satya164

@​react-navigation/bottom-tabs@​7.16.0

7.16.0 (2026-05-11)

Bug Fixes

• default multiselectable to undefined (cd466d4) - by @​satya164

Features

• add ability to prevent tab bar selection (1930fa0) - by @​satya164
• update native tabs to use the new API in react-native-screens (a12db96) - by @​satya164

Changelog

Sourced from @​react-navigation/bottom-tabs's changelog.

7.18.2 (2026-06-15)

Note: Version bump only for package @​react-navigation/bottom-tabs

7.18.1 (2026-06-14)

Note: Version bump only for package @​react-navigation/bottom-tabs

7.18.0 (2026-06-11)

Features

• deprecate navigate object overload (66b5164) - by @​satya164

7.17.2 (2026-06-09)

Note: Version bump only for package @​react-navigation/bottom-tabs

7.17.1 (2026-06-08)

Note: Version bump only for package @​react-navigation/bottom-tabs

7.17.0 (2026-06-07)

Bug Fixes

• flash while switching native bottom tabs with lazy (#13133) (0ae1adb), closes #13132 - by @​dylancom

Features

• add createXScreen helpers to navigators (8b7c2d7) - by @​satya164

7.16.2 (2026-05-25)

Bug Fixes

• default lazy to true for native tabs to avoid flicker (ca4ac56) - by @​satya164

7.16.1 (2026-05-14)

Note: Version bump only for package @​react-navigation/bottom-tabs

7.16.0 (2026-05-11)

Bug Fixes

• default multiselectable to undefined (cd466d4) - by @​satya164

Features

... (truncated)

Commits

• f4af343 chore: publish
• c9ddec7 chore: publish
• d1f2a06 chore: publish
• 66b5164 feat: deprecate navigate object overload
• 83cf9bf chore: publish
• dd325d6 chore: publish
• 8ac4d5e chore: upgrade bob
• 7347d36 chore: upgrade bob
• a103913 chore: publish
• 0ae1adb fix: flash while switching native bottom tabs with lazy (#13133)
• Additional commits viewable in compare view

Updates @react-navigation/native from 7.2.2 to 7.3.3

Release notes

Sourced from @​react-navigation/native's releases.

@​react-navigation/native@​7.3.2

7.3.2 (2026-06-14)

Bug Fixes

• rollback history if update was prevented (045720a) - by @​satya164

@​react-navigation/native@​7.3.0

7.3.0 (2026-06-08)

Features

• add standard navigation compatibility (#13122) (1c26703) - by @​satya164

@​react-navigation/native@​7.2.6

7.2.6 (2026-06-07)

Bug Fixes

• add a workaround for false positive with multiple linking error (301b3a1) - by @​satya164

@​react-navigation/native@​7.2.4

7.2.4 (2026-05-08)

Bug Fixes

• fix linking prefix matching host with additional characters (680a3eb) - by @​satya164
• fix URLs with hashes not being matched correctly (5a884b1) - by @​satya164
• handle errors in parsing query params gracefully (ec42524) - by @​satya164

Changelog

Sourced from @​react-navigation/native's changelog.

7.3.3 (2026-06-15)

Note: Version bump only for package @​react-navigation/native

7.3.2 (2026-06-14)

Bug Fixes

• rollback history if update was prevented (045720a) - by @​satya164

7.3.1 (2026-06-11)

Note: Version bump only for package @​react-navigation/native

7.3.0 (2026-06-08)

Features

• add standard navigation compatibility (#13122) (1c26703) - by @​satya164

7.2.6 (2026-06-07)

Bug Fixes

• add a workaround for false positive with multiple linking error (301b3a1) - by @​satya164

7.2.5 (2026-05-25)

Note: Version bump only for package @​react-navigation/native

7.2.4 (2026-05-08)

Bug Fixes

• fix linking prefix matching host with additional characters (680a3eb) - by @​satya164
• fix URLs with hashes not being matched correctly (5a884b1) - by @​satya164
• handle errors in parsing query params gracefully (ec42524) - by @​satya164

7.2.3 (2026-05-07)

Note: Version bump only for package @​react-navigation/native

Commits

• f4af343 chore: publish
• 6a17f49 refactor: avoid relying on sync update for prevent remove check
• c9ddec7 chore: publish
• 045720a fix: rollback history if update was prevented
• d1f2a06 chore: publish
• dd325d6 chore: publish
• 8ac4d5e chore: upgrade bob
• 1c26703 feat: add standard navigation compatibility (#13122)
• 7347d36 chore: upgrade bob
• a103913 chore: publish
• Additional commits viewable in compare view

Updates @react-navigation/native-stack from 7.14.12 to 7.17.5

Release notes

Sourced from @​react-navigation/native-stack's releases.

@​react-navigation/native-stack@​7.17.0

7.17.0 (2026-06-07)

Features

• add createXScreen helpers to navigators (8b7c2d7) - by @​satya164

@​react-navigation/native-stack@​7.16.0

7.16.0 (2026-05-25)

Features

• add prop for disabling default top inset application (#13114) (40b7e21) - by @​t0maboro

@​react-navigation/native-stack@​7.15.0

7.15.0 (2026-05-11)

Bug Fixes

• default multiselectable to undefined (cd466d4) - by @​satya164

Features

• update native tabs to use the new API in react-native-screens (a12db96) - by @​satya164

Changelog

Sourced from @​react-navigation/native-stack's changelog.

7.17.5 (2026-06-15)

Note: Version bump only for package @​react-navigation/native-stack

7.17.4 (2026-06-14)

Note: Version bump only for package @​react-navigation/native-stack

7.17.3 (2026-06-11)

Note: Version bump only for package @​react-navigation/native-stack

7.17.2 (2026-06-09)

Note: Version bump only for package @​react-navigation/native-stack

7.17.1 (2026-06-08)

Note: Version bump only for package @​react-navigation/native-stack

7.17.0 (2026-06-07)

Features

• add createXScreen helpers to navigators (8b7c2d7) - by @​satya164

7.16.0 (2026-05-25)

Features

• add prop for disabling default top inset application (#13114) (40b7e21) - by @​t0maboro

7.15.1 (2026-05-14)

Note: Version bump only for package @​react-navigation/native-stack

7.15.0 (2026-05-11)

Bug Fixes

• default multiselectable to undefined (cd466d4) - by @​satya164

Features

• update native tabs to use the new API in react-native-screens (a12db96) - by @​satya164

7.14.14 (2026-05-08)

Note: Version bump only for package @​react-navigation/native-stack

... (truncated)

Commits

• f4af343 chore: publish
• c9ddec7 chore: publish
• d1f2a06 chore: publish
• 83cf9bf chore: publish
• dd325d6 chore: publish
• 8ac4d5e chore: upgrade bob
• 7347d36 chore: upgrade bob
• a103913 chore: publish
• 8b7c2d7 feat: add createXScreen helpers to navigators
• b89bba2 chore: publish
• Additional commits viewable in compare view

Updates @reduxjs/toolkit from 2.11.2 to 2.12.0

Release notes

Sourced from @​reduxjs/toolkit's releases.

v2.12.0

This feature release adds RTK usage skills files (via TanStack Intent) exports the RTK Query hook options types for reusability, fixes issues with infinite query status flags and batching handling, and makes some small TS improvements.

Changelog

Skills Files

We've generated agent skill files that are now included in the RTK package itself in a skills folder. They cover using and migrating to modern RTK, client and server state management, and handling side effects. You can point your agent at these skills yourself, or use TanStack Intent to pick them up.

TypeScript Improvements

The types for our RTK Query hook options are now exported, which lets you stop using Parameters to extract those types for use in your own code.

The types for listener middleware matchers were tweaked to allow interface-based type guards, not just type-based definitions.

The internal IgnorePaths type was renamed to IgnoredPaths for consistency.

We now use the built-in NoInfer util that comes with TS 5.4+.

Fixes

We fixed handling of the isSuccess status flag when switching infinite query cache entries. This should prevent accidental UI flashes that were occurring due to this flag accidentally flipping.

We've added a 100ms timeout fallback to the autoBatch enhancer's requestAnimationFrame timer. We had several reports that rAF didn't work correctly when used in background tabs / opened windows, and that RTK never updated the UI. This should ensure that the updates flush correctly.

What's Changed

• Export hook options types for RTK Query hooks by @​veeceey in reduxjs/redux-toolkit#5218
• Add TanStack Intent skills for Redux Toolkit by @​phryneas in reduxjs/redux-toolkit#5249
• Keep isSuccess: true when switching infinite query cache entries by @​riqts in reduxjs/redux-toolkit#5268
• fix: allow interface-based type guards as listener matcher by @​riqts in reduxjs/redux-toolkit#5269
• fix: add setTimeout fallback to raf autoBatch strategy for background tabs by @​riqts in reduxjs/redux-toolkit#5273
• chore(toolkit): rename IgnorePaths type to IgnoredPaths by @​Ri5ha6h in reduxjs/redux-toolkit#5284
• feat(toolkit)!: switch to native NoInfer utility type by @​aryaemami59 in reduxjs/redux-toolkit#5289

Full Changelog: reduxjs/redux-toolkit@v2.11.2...v2.12.0

Commits

• 576a02f Release 2.12.0
• de2d55e Merge pull request #5237 from aryaemami59/fix/codegen/generateEndpoints-retur...
• ac807c3 fix(codegen): narrow generateEndpoints return type
• 01ed3ba Merge pull request #5289 from aryaemami59/feat/toolkit/switch-to-native-NoInfer
• 1f16db1 Merge pull request #5290 from aryaemami59/build/toolkit/exclude-test-files-fr...
• 23783c1 build(toolkit): exclude test files from final bundle
• 91b8b0a feat(toolkit)!: switch to native NoInfer utility type
• 0b37f1a Merge pull request #5286 from aryaemami59/docs/toolkit/fix-typos
• 3cd62c8 fix unforwardedActions
• 64853cc chore: fix various typos
• Additional commits viewable in compare view

Updates @shopify/flash-list from 2.3.1 to 2.3.2

Release notes

Sourced from @​shopify/flash-list's releases.

v2.3.2

What's Changed

• fix(recycling): disable removeClippedSubviews to prevent Android crash by @​shopify-github-actions-access[bot] in Shopify/flash-list#2202
• fix: scroll to index autoscroll race by @​isekovanic in Shopify/flash-list#2290
• feat(sticky-headers): configure sticky header zIndex by @​GurkarnSD in Shopify/flash-list#2311

New Contributors

• @​isekovanic made their first contribution in Shopify/flash-list#2290
• @​GurkarnSD made their first contribution in Shopify/flash-list#2311

Full Changelog: Shopify/flash-list@v2.3.1...v2.3.2

Commits

• 8c1375e v2.3.2
• d6c9513 feat(sticky-headers): configure sticky header zIndex (#2311)
• 8ca7477 fix: scroll to index autoscroll race (#2290)
• f4278ba Update skill to include fixture checks
• 8bf4c81 chore(deps): bump picomatch from 2.3.1 to 2.3.2 in /fixture/web (#2210)
• ea9956a chore(deps): bump picomatch from 2.3.1 to 2.3.2 (#2214)
• 43ed94e chore(deps): bump picomatch from 2.3.1 to 2.3.2 in /documentation (#2212)
• 508606e chore(deps): bump picomatch from 2.3.1 to 2.3.2 in /fixture/react-native (#2213)
• f47a64e chore(skills): add analyze-feedback skill and incorporate agent learnings (#2...
• 5ffed99 feat(skills): add analyze-feedback skill for agent workflow feedback (#2206)
• Additional commits viewable in compare view

Updates fuse.js from 7.3.0 to 7.4.2

Release notes

Sourced from fuse.js's releases.

v7.4.2

Bug Fixes

• types: ship CommonJS type declarations (.d.cts) so consumers on moduleResolution: node16/nodenext no longer hit TS1479 ("masquerading as ESM") when importing the package from a CommonJS project. The lib entries now resolve to a runtime-accurate export = declaration and the worker to its named declaration, via the require exports condition. (#780)

Full Changelog: krisk/Fuse@v7.4.1...v7.4.2

v7.4.1

Bug Fixes

• types: ship TypeScript declarations for fuse.js/worker (572ad1e), closes #828
• types: add TypeScript declarations for fuse.js/worker-script (6ef6c33), closes #828

Both worker subpaths now resolve types under node16/nodenext and bundler module resolution.

v7.4.0

First stable on the 7.4 line. Aggregates everything from the 7.4.0-beta.1 → 7.4.0-beta.8 cycle. See CHANGELOG.md for the per-beta breakdown.

Features

• FuseWorker — parallel search via Web Workers (9ba192c). New FuseWorker class shards the collection across workers, runs searches in parallel, and preserves the same result ordering as Fuse. See the Web Workers guide.
• token-search: tokenMatch: 'all' | 'any' option for AND/OR semantics (#827, 9f979d0). Default 'any' preserves existing behavior; 'all' requires every query word to match somewhere in a record (term-centric AND), useful for filter-style queries.
• token-search: customizable tokenizer with unicode-aware default (#821, 8e55cae). New tokenize?: RegExp | (text: string) => string[] option; the default regex now segments CJK, Cyrillic, Greek, Arabic, etc. out of the box.

Bug Fixes

• matches: report array-path keys as dotted strings (acd54e8). Previously match.key leaked a raw string[] for keys declared as path arrays (e.g. keys: [['author', 'firstName']]), contradicting the documented FuseResultMatch.key: string type. Now emits the canonical dotted string ('author.firstName'). Behavior change: consumers relying on the array shape need to update.
• bitap: restrict highlight indices to matched window (#792, 622f105). Closes #505, #611, #691, #793.
• index: correct doc-index alignment for Fuse<string> with blank docs (0b8e3ca).
• core: invalidate searcher cache on collection mutation (fcf4228).
• token-search: renumber inverted index after doc removal (ea9356d).
• workers: preserve global refIndex across shards (e4217f9), match Fuse ordering and reject non-cloneable options (d571390), reject useTokenSearch in FuseWorker (8c6183d).
• match: explicitly reject useTokenSearch in Fuse.match (3959d91).
• correct fieldCount accounting and add reverse lookup in inverted index (54e702c).
• guard against empty-string crash in fieldNorm (e550ab1); skip consecutive spaces in fieldNorm word counting (5929af6).
• types: resolve typecheck errors and align KeyStore types (dbc115d).
• docs: reflect data edits in playground demo (#825, 6eff909).

Performance

• reuse bit arrays in Bitap search instead of allocating per error level (ec9b446)
• replace forEach with for loops in search hot paths (1945f49)
• fast-path Math.pow when exponent is 1 in computeScore (c82de57)
• pre-allocate records array and use for loops in FuseIndex.create (5800036)
• replace regex with loop for word counting in fieldNorm (5517a9b)
• use filter instead of reverse-splice in removeAll / remove (c74823b, 8372b0a)
• token-search: drop unused postings from inverted index (5ea216f)

Internal

... (truncated)

Changelog

Sourced from fuse.js's changelog.

7.4.2 (2026-06-05)

Bug Fixes

• types: emit CommonJS declarations (.d.cts) for node16/nodenext (#780) (33f5d29)

7.4.1 (2026-06-02)

Bug Fixes

• types: add TypeScript declarations for fuse.js/worker-script (6ef6c33), closes #828
• types: ship TypeScript declarations for fuse.js/worker (572ad1e), closes #828

7.4.0 (2026-05-30)

7.4.0-beta.8 (2026-05-25)

Bug Fixes

• matches: report array-path keys as dotted strings (acd54e8)

7.4.0-beta.7 (2026-05-22)

Features

• token-search: add tokenMatch 'all' | 'any' for AND/OR (#827) (9f979d0)

Bug Fixes

• docs: reflect data edits in playground demo (#825) (6eff909)

7.4.0-beta.6 (2026-05-14)

Bug Fixes

• bitap: restrict highlight indices to matched window (622f105), closes #792 #505 #611 #691 #793

7.4.0-beta.5 (2026-05-10)

Features

• token-search: add customizable tokenizer with unicode-aware default (8e55cae), closes #821

... (truncated)

Commits

• 9e63058 chore(release): 7.4.2
• 33f5d29 fix(types): emit CommonJS declarations (.d.cts) for node16/nodenext (#780)
• 7c6af4e build: replace rollup/babel/terser build with tsdown
• 50f6b24 chore(deps): pin fast-uri to ^3.1.2 via overrides
• 9e6ec22 chore(build): exit non-zero when a build step fails
• ff51f6b chore: source docs version from package.json, not npm view
• 08b77d9 chore: bump doc versions to 7.4.1
• ce75998 chore(release): 7.4.1
• e842baf test(types): guard that every exports subpath resolves to declarations
• 6ef6c33 fix(types): add TypeScript declarations for fuse.js/worker-script
• Additional commits viewable in compare view

Updates i18next from 26.0.8 to 26.3.1

Release notes

Sourced from i18next's releases.

v26.3.1

• 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

• 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

• 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

• 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

• 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

• 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

Changelog

Sourced from i18next's changelog.

26.3.1

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

26.3.0

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

26.2.0

• 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)

26.1.0

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

26.0.10

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

  Description has been truncated