[dependabot]

Bumps the frontend-minor-patch group with 16 updates in the / directory:

Package	From	To
@azure/msal-browser	5.6.3	5.23.0
@mui/x-tree-view	9.1.0	9.14.0
canvas	3.2.2	3.2.3
dompurify	3.4.5	3.4.16
echarts	6.0.0	6.1.0
i18next	26.0.1	26.4.2
katex	0.16.42	0.19.0
react-animate-height	3.2.3	3.2.4
react-arborist	3.7.0	3.16.0
react-virtuoso	4.18.3	4.18.16
validator	13.15.26	13.15.35
vega	6.2.0	6.4.0
vega-lite	6.4.1	6.4.3
@testing-library/dom	10.4.1	10.4.2
@testing-library/react	16.3.2	16.3.3
@types/lodash	4.17.24	4.17.25

Updates @azure/msal-browser from 5.6.3 to 5.23.0

Release notes

Sourced from @​azure/msal-browser's releases.

@​azure/msal-browser v5.23.0

5.23.0

Wed, 23 Sep 2026 15:49:43 GMT

Minor changes

• Add Native Auth V2 password reset, sign-in, sign-up, and SMS MFA flows. #8830 (yongdiwang@microsoft.com)
• Add platform broker DPoP request and response contract support #8772 (hectormmg@microsoft.com)
• Export shared web broker bridge performance event names. #8832 (shylasummers@microsoft.com)

Patches

• Treat bfcache restoration during redirects as user cancellation #8839 (thomas.norling@microsoft.com)
• Preserve the requested resource when caching platform broker access tokens #8848 (nugetaad@microsoft.com)

@​azure/msal-browser v5.22.0

5.22.0

Tue, 15 Sep 2026 19:42:08 GMT

Minor changes

• Export shared web broker bridge runtime utilities from the package root. #8792 (shylasummers@microsoft.com)
• Bump @​azure/msal-common to v16.14.1 (beachball)

Patches

• Fix flaky timestamp validation in unit tests #8796 (kshabelko@microsoft.com)

@​azure/msal-browser v5.21.0

5.21.0

Wed, 02 Sep 2026 21:15:30 GMT

Minor changes

• Validate the relayed request in runPopupRelay before navigating and add an optional allowedAuthorityOrigins pin #8800 (kshabelko@microsoft.com)

@​azure/msal-browser v5.20.0

5.20.0

Fri, 28 Aug 2026 21:29:53 GMT

Minor changes

• Enable browser-native PublicClientApplication DPoP acquisition flows #8735 (hectormmg@microsoft.com)
• Export IWebBrokerBridgeMessage from the msal-browser package root #8780 (shylasummers@microsoft.com)
• Bump @​azure/msal-common to v16.14.0 (beachball)

... (truncated)

Commits

• 23eccba NAA + Encrypted Authorize Response (EAR) e2e tests (#8799)
• addecb9 [NAA/PWB One Bridge] PR 6/6 companion: Share bridge performance event names (...
• fe9de8e Remove acquireTokenInteractive responseMode in v7 (#8852)
• dad91a3 Deprecate acquireTokenInteractive responseMode (#8851)
• dc25191 Fix platform broker cache isolation by resource (#8848)
• 193e100 feat(msal-browser): add Native Auth V2 flows (#8830)
• 6875947 Fix redirect cancellation after bfcache restore (#8839)
• 8228a8b Fix cache-only upgrade and downgrade transitions (#8853)
• f791edc Coalesce msal-node silent requests (#8811)
• 5c78da1 Platform Broker + Keep Me Signed In e2e tests (#8822)
• Additional commits viewable in compare view

Updates @mui/x-tree-view from 9.1.0 to 9.14.0

Release notes

Sourced from @​mui/x-tree-view's releases.

v9.14.0

We'd like to extend a big thank you to the 16 contributors who made this release possible. Here are some highlights ✨:

• 🌍 Add Hebrew (he-IL) locale to the Scheduler
• 📅 Scheduler time grid now opens at 7 AM by default, configurable with the new initialScrollTime prop
• 🗓️ Auto-scheduling engine for finish-to-start dependencies in the Premium Event Timeline
• 🧩 New content slots for the Event Timeline event block and resource title cell
• ♿️ Charts announce the visible zoom range to screen readers
• 🐞 Bugfixes
• 📚 Documentation improvements

Special thanks go out to these community members for their valuable contributions: @​eterry1388, @​jamesDin, @​kareem-ib, @​mateuseap, @​mustafajw07

The following team members contributed to this release: @​arminmeh, @​bernardobelchior, @​brijeshb42, @​flaviendelangle, @​hasdfa, @​Janpot, @​JCQuintas, @​MBilalShafi, @​michelengelen, @​noraleonte, @​rita-codes

Data Grid

@mui/x-data-grid@9.14.0

• [DataGrid] Do not crash on unmount when the document has no body (#23431) @​eterry1388
• [DataGrid] Fix MissingRowIdError on cell mousedown/mouseup after row removal (#23261) @​kareem-ib
• [DataGrid] Fix quick filter dropping a pending search on parser identity change (#23575) @​michelengelen
• [DataGrid] Keep overlays sticky in RTL mode (#23492) @​arminmeh
• [DataGrid] Prevent scroll area state update before mount (#23478) @​michelengelen
• [DataGrid] Remove 'menu' role from the actions cell (#23437) @​michelengelen

@mui/x-data-grid-pro@9.14.0

Same changes as in @mui/x-data-grid@9.14.0, plus:

• [DataGridPro] Fix data integrity issue in nested server data (#23518) @​MBilalShafi
• [DataGridPro] Keep parent selection when lazily loaded children arrive (#23421) @​michelengelen

@mui/x-data-grid-premium@9.14.0

Same changes as in @mui/x-data-grid-pro@9.14.0.

Date and Time Pickers

@mui/x-date-pickers@9.14.0

Internal changes.

@mui/x-date-pickers-pro@9.14.0

Same changes as in @mui/x-date-pickers@9.14.0.

Charts

... (truncated)

Changelog

Sourced from @​mui/x-tree-view's changelog.

9.14.0

Sep 17, 2026

We'd like to extend a big thank you to the 16 contributors who made this release possible. Here are some highlights ✨:

• 🌍 Add Hebrew (he-IL) locale to the Scheduler
• 📅 Scheduler time grid now opens at 7 AM by default, configurable with the new initialScrollTime prop
• 🗓️ Auto-scheduling engine for finish-to-start dependencies in the Premium Event Timeline
• 🧩 New content slots for the Event Timeline event block and resource title cell
• ♿️ Charts announce the visible zoom range to screen readers
• 🐞 Bugfixes
• 📚 Documentation improvements

Special thanks go out to these community members for their valuable contributions: @​eterry1388, @​jamesDin, @​kareem-ib, @​mateuseap, @​mustafajw07

The following team members contributed to this release: @​arminmeh, @​bernardobelchior, @​brijeshb42, @​flaviendelangle, @​hasdfa, @​Janpot, @​JCQuintas, @​MBilalShafi, @​michelengelen, @​noraleonte, @​rita-codes

Data Grid

@mui/x-data-grid@9.14.0

• [DataGrid] Do not crash on unmount when the document has no body (#23431) @​eterry1388
• [DataGrid] Fix MissingRowIdError on cell mousedown/mouseup after row removal (#23261) @​kareem-ib
• [DataGrid] Fix quick filter dropping a pending search on parser identity change (#23575) @​michelengelen
• [DataGrid] Keep overlays sticky in RTL mode (#23492) @​arminmeh
• [DataGrid] Prevent scroll area state update before mount (#23478) @​michelengelen
• [DataGrid] Remove 'menu' role from the actions cell (#23437) @​michelengelen

@mui/x-data-grid-pro@9.14.0

Same changes as in @mui/x-data-grid@9.14.0, plus:

• [DataGridPro] Fix data integrity issue in nested server data (#23518) @​MBilalShafi
• [DataGridPro] Keep parent selection when lazily loaded children arrive (#23421) @​michelengelen

@mui/x-data-grid-premium@9.14.0

Same changes as in @mui/x-data-grid-pro@9.14.0.

Date and Time Pickers

@mui/x-date-pickers@9.14.0

Internal changes.

@mui/x-date-pickers-pro@9.14.0

... (truncated)

Commits

• c83b3dd [release] v9.14.0 (#23608)
• b3f1639 [tree view] Prune stale children when replacing an item's children (#23598)
• 721668f [tree view] Optimize lazy loading store writes for nested children (#23489)
• c2809ca [release] v9.13.0 (#23497)
• b5c78e1 [tree view] Remove dead UI from community component (#23487)
• 6b7f6e3 [tree view] Remove unused dependencies (#23488)
• 3e080e5 [tree view] Add loading prop and customizable loading UI (#22251)
• 36c2a0a [code-infra] Run TypeScript 7 alongside the TS6 JS API (#23471)
• 846b709 [code-infra] Replace the sinon spy(fn) usages with vi.fn(fn) (#23460)
• f3784e8 [code-infra] Replace the mechanical sinon spy() usages with vi.fn() (#23443)
• Additional commits viewable in compare view

Updates canvas from 3.2.2 to 3.2.3

Release notes

Sourced from canvas's releases.

v3.2.3

Fixed

• Fix building with gcc (#2559)

Changelog

Sourced from canvas's changelog.

3.2.3

Fixed

• Fix building with gcc (#2559)

Commits

• f91598e v3.2.3
• 1541544 PAGE_SIZE shouldn't be unsigned
• See full diff in compare view

Updates dompurify from 3.4.5 to 3.4.16

Release notes

Sourced from dompurify's releases.

DOMPurify 3.4.16

• Fixed a problem with IN_PLACE node removal when working with hooks, thanks @​manus-pi
• Fixed a problem with IN_PLACE sanitization and raw-text roots, thanks @​h-t-m
• Fixed a problem with ESM default exports landing in CommonJS declarations, thanks @​ssi02014
• Migrated from rollup to rolldown because performance, thanks @​ssi02014
• Bumped several dependencies where possible

DOMPurify 3.4.15

• Added better clobbering hardening when XML content is involved, thanks @​gnyselcuk
• Added several smaller hardening and edge-case improvements, thanks @​leechristensen
• Bumped several dependencies where possible

DOMPurify 3.4.14

• Fixed an issue with possible bypasses when risky tags are allow-listed, thanks @​AlirezaRouhbakhsh
• Fixed a couple of edge cases with mixed document contexts, thanks @​fishjojo1
• Added the SVG pointer-events and vector-effect presentation attributes to the allow-list, thanks @​Jaybhade
• Conducted another refactoring run, removed dead branches and duplicated logic, flattened attribute validation
• Updated the documentation in several spots, README, wiki, etc., thanks @​Akokonunes
• Updated several development dependencies and CI workflow actions

DOMPurify 3.4.13

• Fixed an issue with hook removal during IN_PLACE sanitization, thanks @​koyokr
• Fixed an issue with hooks potentially bypassing the clone guard, thanks @​AkshayjainG
• Fixed an issue with DOM clobbering via ownerDocument during IN_PLACE, thanks @​AkshayjainG
• Bumped several dependencies where possible

DOMPurify 3.4.12

• Fixed an issue where a hook would not get called for custom elements, thanks @​Rikuxx0
• Hardened the handling of hooks removing elements, @​mkrause-bee360
• Added support for a few new SVG attributes, thanks @​cbn-falias & @​Develop-KIM
• Hardened the handling of declarative partial updates
• Updated the documentation is several spots, README, wiki, etc.
• Bumped several dependencies where possible

DOMPurify 3.4.11

• Fixed an issue with a leaky config for hooks via setConfig, thanks @​trace37labs
• Bumped vulnerable development dependencies to arrive at plain 0 with npm audit
• Updated the osv-scanner suppression list as no vulnerable dependencies are left for now
• Updated up the linting tool-chain and removed now-redundant lint directives
• Updated the documentation is several spots, README, wiki, etc.
• Bumped several dependencies where possible

DOMPurify 3.4.10

• Refactored codebase for clarity: extracted the public type declarations into types.ts
• Decomposed the three largest sanitizer functions into focused helpers
• Removed duplicated defaults and dead branches, consolidated SAFE_FOR_TEMPLATES scrubbing into single shared path
• Improved per-node performance by hoisting the mXSS probe regexes and testing textContent before innerHTML
• Added a deterministic micro-benchmark harness (npm run bench) with a --compare mode
• Reduced CI cost by running the full three-engine browser suite once per PR
• Refreshed the demos/ folder so every demo runs again, and added a SVG-via-<img> demo

... (truncated)

Commits

• b9b9d80 release: 3.4.16 (#1636)
• 1d7460c release: 3.4.15 (#1609)
• 4e6fe24 release: 3.4.14 (#1587)
• 3067f77 release: 3.4.13 (#1562)
• a9ca1e5 release: 3.4.12 (#1537)
• 0cae518 release: 3.4.11 (#1494)
• 6ee5716 release: 3.4.10 (#1478)
• 5210247 release: 3.4.9 (#1459)
• bcdd828 release: 3.4.8 (#1439)
• ca30f07 release: 3.4.7 (#1414)
• Additional commits viewable in compare view

Updates echarts from 6.0.0 to 6.1.0

Release notes

Sourced from echarts's releases.

6.1.0

• [Feature] [axis] Support dataMin and dataMax option for calculating a nice axis extent. #20838 (Justin-ZS, Ovilia)
• [Feature] [axis] Comprehensively enable all types of axis (i.e., "value"/"time"/"category"/"log") to render series (typically "bar"/"pictorialBar"/"candlestick"/"boxplot") without overflow (including the case "category" axis with boundaryGap: false); provide containShape option; provide some corresponding clip option. dbfaf6a73 fe932a2aa 3973b21ee (100pah) #21511 (Akash Sonune)
• [Feature] [axis] Automatically exclude non-positive series data values on "log" axis. dedc5dc18 (100pah)
• [Feature] [axis] Enable axisLabel.formatter to receive its index for working with customValues. #21220 #21432 (Szymon Pachucki, Ovilia, plainheart)
• [Feature] [line] Add triggerEvent option for more control over mouse event. #21001 (Steven Cobb, plainheart)
• [Feature] [pie] Add tangential-noflip rotation mode to keep labels tangential without flipping. #21258 (春秋半夏, Ovilia)
• [Feature] [gauge] progress.color supports 'auto'. #21224 (StNimmerlein, Ovilia)
• [Feature] [radar] Add clockwise option. #21143 (Dai Xuezhou, Ovilia)
• [Feature] [candlestick] [dataZoom] Add cursor option for candlestick series and add cursorGrab option & cursorGrabbing for 'inside' dataZoom. #21558 (zuming, Ovilia, 100pah)
• [Feature] [scatter] [effectScatter] [geo] Enable clip option on "scatter"/"effectScatter" on geo. 417592289 (100pah)
• [Feature] [visualMap] Add seriesTargets option for multiple series-dimension mappings. #20703 (Justin-ZS, plainheart)
• [Feature] [matrix] Support matrix.x/y.length for conveniently creating a headless matrix without composing an array. #21191 (100pah, plainheart)
• [Feature] [matrix] Add triggerEvent option to support triggering event on matrix cells. #21390 (Natsuo Kawai, 100pah)
• [Feature] [i18n] add Latvian(LV) translation. #21546 (EPoikans)
• [Fix] [axis] Change and clarify the rounding error and auto-precision utils and solutions. 479dcd454 (100pah)
• [Fix] [axis] Fix chart does not work when using customValues with formatter in time axis (axis.type: 'time') label. #21352 (Srajan Sanjay Saxena, plainheart)
• [Fix] [axis] Fix and clarify alignTick strategy, and fix LogScale precision. a6ab2458f ffcc636fb (100pah)
• [Fix] [axis] Fix duplicate ticks when using time axis (axis.type: 'time') or customValues, which causes jitter of splitArea; fix the showMin/MaxLabel handling of a category axis (axis.type: 'category'); enable a uniform bandWidth calculation in numeric axis (axis.type: 'value' | 'time' | 'log'). 8de2b64fa 15af0db02 8ddaa5c69 (100pah)
• [Fix] [axis] Fix time axis (axis.type: 'time') bug when value scale is in millisecond. 40b77b464 (100pah)
• [Fix] [bar] Fix wrong label position when bar series has a 0 width/height. #21218 (Justin-ZS, Ovilia)
• [Fix] [scatter] Fix jitter layout does not support progressive rendering and cause chart to be frozen and potential NPE. #21436 (plainheart)
• [Fix] [lines] Fix effect symbol flip on unidirectional loop end when roundTrip is not enabled. #21320 (Mayank Mehta, plainheart)
• [Fix] [candlestick] Fix candlestick render error with series.encode on horizontal layout. #21325 (Purbayan Pramanik, 100pah)
• [Fix] [parallel] Fix incorrect axis extent when any subsequent series has a larger value than the first. #21387 (jackhickson, 100pah)
• [Fix] [pie] Support axes extent union pie center automatically when pie is laid out on Cartesian (grid component). 18a23a875 (100pah)
• [Fix] [treemap] Fix treemap can not be zoomed out after a zoom-in when scaleLimit is specified #21427 (TateLiu, 100pah)
• [Fix] [lines] Fix potential tooltip XSS vulnerability in lines series (series.type: 'lines'). #21608 (plainheart)
• [Fix] [map] [geo] Fix the failed synchronization and visual artifacts on geo roaming and animation. 417592289 (100pah)
• [Fix] [tooltip] Fix tooltip content does not refresh when changing tooltip trigger from 'axis' to 'item'. #20710 (Justin-ZS, plainheart)
• [Fix] [tooltip] valueFormatter callback param dataIndex should be rawDataIndex rather than dataZoom filtered dataIndex. #21479 (100pah, plainheart)
• [Fix] [axisPointer] Fix axisPointer shadow and enable clipping - it is previously only applicable to "category" axis, but is buggy in numeric axis with "bar" series. 8de2b64fa (100pah)
• [Fix] [axisPointer] Fix visual artifacts caused by failed axisPointer restoration. 56a32c0bb (100pah)
• [Fix] [hoverLayer] Fix visual artifacts arisen on hover layer. zrender#1151 933585126 (100pah)
• [Fix] [marker] Fix marker fails to render with dataset and encode. #21439 (plainheart, 100pah).
• [Fix] [dataZoom] Fix wrong position of the dataZoom when the series has only one data point. #21196 (alesmit, Ovilia)
• [Fix] [dataZoom] Fix dataZoom bug that data info disappears when dragging released; fix dataZoom dragging cursor style. 64305a4b8 (100pah)
• [Fix] [dataZoom] Apply a better auto-precision method; fix unexpected behaviors when dataZoom controls axes with alignTicks: true. d168bf237 (100pah)
• [Fix] [dataZoom] Fix AxisProxy can not be cleared when dataZoom option changed; fix related onZero behaviors. 52ceb924a 2e82d33c3 (100pah)
• [Fix] [areaStyle] Fix areaStyle render error when dimension name is empty string. #21219 (Justin-ZS, Ovilia)
• [Fix] [sunburst] Fix root node label may not be centered. #21306 (Akash Sonune, Ovilia)
• [Fix] [matrix] Fix matrix label formatter does not work. #21410 (Justin-ZS, Ovilia)
• [Fix] [toolbox] Fix emphasis color is the same as the default color. #21384 (Ovilia) b094f987d (100pah)
• [Fix] [toolbox] Fix the dataView component does not fit the dark mode. #21176 (notthistrain, Ovilia)
• [Fix] [progressive] Fix progressive rendering issues. 91a60fc76 (100pah)
• [Fix] [labelLine] Fix labelLine.smooth can not be reset. #21425 (fanwww, plainheart)
• [Fix] [graphic] Fix stroke corner gap due to not closing path in roundRect helper. zrender#1155 (plainheart)
• [Fix] [svg] Enhance SVG encodeBase64 compatibility to make it available in more environments like Web Worker/NodeJS/Bun. zrender#1145 (plainheart)
• [Fix] [core] Mark echarts instance object as raw in Vue. #21293 (plainheart)
• [Fix] [chord] Add the missing export entry for chord chart. #21197 (plainheart, Ovilia)

... (truncated)

Commits

• c5a48f5 Merge pull request #21612 from apache/release-dev
• 77e5222 release 6.1.0-rc.2
• 21f17be fixRegression(map,geo): Resolve circular dependencies introduced by this vers...
• 830e8b6 chore: Supplement package.json (for module cjs declaration) to source release.
• ed0e210 chore: Fix addHeader tool and add missing license headers.
• cc78ada Merge pull request #21611 from apache/release-dev
• 3f6e012 release: Build release.
• d69405f chore: Add missing headers.
• 6998ed0 release: Upgrade npm version.
• 8cb374b fix(build): Fix build commands.
• Additional commits viewable in compare view

Updates i18next from 26.0.1 to 26.4.2

Release notes

Sourced from i18next's releases.

v26.4.2

• fix: $&, $`, $' and $$ inside a nested value ($t(key)) now stay literal. nest() handed the resolved value straight to String.replace as the replacement argument, so those sequences were read as replacement patterns: $& re-inserted the $t(...) match, $` / $' inserted the text before / after it, and $$ collapsed to $. Through t() the $& case was worse than a wrong string: the nested lookup resets the shared nesting regexp, so the re-inserted $t(...) was matched again on every pass and t() never returned — also under the default escapeValue: true when the value arrives via a variable forwarded through nesting options ($t(key, { "name": "{{name}}" }) with a name containing $&). The value is now $-escaped at the String.replace call, the same guard interpolate() already has, and a non-string value returned by a formatter in the nesting chain ($t(key, myFormat)) is stringified before that. Nested values are still not HTML-escaped (#854). Thanks @​mahirhir (#2447).

v26.4.1

• fix(types): the selector-form keyPrefix overload of getFixedT() is now available under enableSelector: 'strict'. Its constraint was gated on true | 'optimize' only, so under 'strict' it collapsed to never, the overload dropped out, and the returned t silently lost its keyPrefix scope (t(($) => $.deep) failed with Property 'deep' does not exist on type '{}'). The same call already typechecked under true and 'optimize'. Thanks @​hovelopin (#2446).

v26.4.0

• perf: cache toResolveHierarchy results per (code, fallbackCode) pair. The hierarchy resolver runs on every t() call and calls Intl.getCanonicalLocales multiple times, which showed up prominently when profiling render-heavy UIs (e.g. virtualized data grids); with the cache the per-call cost drops from ~886 ns to ~41 ns. The cache is invalidated automatically when options.fallbackLng changes (reassignment or in-place array mutation); if you mutate other resolution-relevant options at runtime (load, lowerCaseLng, cleanCode, nonExplicitSupportedLngs), call i18next.services.languageUtils.clearCache() afterwards. Function-valued fallbackLng and per-call array/object fallbackLng options are never cached, so dynamic fallbacks keep working as before. Thanks @​equaterina (#2444).
• chore: update all devDependencies (Babel stays on 7.x until @rollup/plugin-babel supports 8, eslint on 9.x for neostandard). Removed the unused coveralls package (CI uses the Coveralls GitHub Action) and replaced sinon with nise + vitest.spyOn in the v1 compatibility tests, which resolves all open npm audit findings (0 vulnerabilities) and should close the dependabot alerts on the lockfile.

v26.3.6

• fix: allow TypeScript 7 in the optional typescript peer dependency range (^5 || ^6 || ^7). With typescript@7.0.2 in a project, npm install failed with an ERESOLVE peer conflict. The published types are TS7-compatible as-is: every test/typescript suite produces identical results under 6.0 and 7.0.2. Reported in react-i18next#1927, thanks @​andikapradanaarif.

v26.3.5

• fix: $t() nesting options blocks that span multiple lines are now parsed. nest() decided where the nested key ends by testing match[1] with /{.*}/, whose dot does not cross line breaks — so a $t(key, { ... }) options object containing a newline was treated as having no options, mis-split as formatters, and the nested lookup ran without its options (placeholders stayed unresolved). The nesting regexp itself already matches newlines inside $t(...); adding the s (dotAll) flag makes multiline options behave like the single-line form. Thanks @​spokodev (#2440).
• fix: getUsedParamsDetails (the returnDetails: true path) no longer mutates the passed replace object. It wrote count straight onto options.replace so the returned usedParams would include it — a caller reusing one replace object across t() calls then carried a stale count into later interpolations (e.g. a previous call's count: 5 rendered instead of the current call's value). The details are now built from a copy; usedParams still includes count. Thanks @​spokodev (#2441).
• fix: with the default skipOnVariables: true + escapeValue: true, a {{placeholder}} carried inside an interpolated value now stays literal even when the value contains escapable characters. The skip logic advanced the regex lastIndex by the raw value length, but the escaped text written into the string is longer, so lastIndex landed inside the inserted value and a trailing {{placeholder}} in it got interpolated — leaking another in-scope variable that should have stayed literal (values without escapable characters were already skipped correctly). The advance now uses the escaped length that is actually written, and the regex-safe $-doubling is applied only at the String.replace call so it can't distort the length arithmetic. Thanks @​spokodev (#2442).

v26.3.4

• fix(security): deepExtend (used by addResourceBundle(..., deep, overwrite)) no longer recurses into inherited properties. It checked key existence with the in operator, which walks the prototype chain, so a source key matching an inherited built-in (e.g. hasOwnProperty, toString) caused recursion into the shared Object.prototype function and, with overwrite: true, could overwrite e.g. Object.prototype.hasOwnProperty.call with a non-callable value — corrupting a shared built-in process-wide (DoS). Existence is now checked with Object.prototype.hasOwnProperty.call, so such keys are copied as plain own data instead. This complements the existing __proto__/constructor guard and is also strictly more correct for an own-property merge. Only affects applications that pass attacker-controlled data with deep: true and overwrite: true; no standard backend/integration does this. Distinct from CVE-2026-48713 / CVE-2026-48714 (different packages, setPath mechanism). Thanks to zx (Jace) for the responsible disclosure.

v26.3.3

• fix(types): selector t($ => $.arr, { returnObjects: true, context }) on a JSON array of heterogeneous objects now preserves each element's full shape (e.g. { transKey1: string; transKey2: string }[]) instead of collapsing to a union of partial element types. Two type-level causes: (1) FilterKeys evaluated the whole array element type at once, so keyof (A | B) only saw the keys common to every element — it now distributes over the object union and filters each element independently; (2) when TypeScript merges mismatched array element types it injects phantom optional undefined keys (e.g. transKey1_withContext?: undefined on elements that don't define it), which the context-detection helpers mistook for real context variants — they now skip keys typed as undefined. Also adds a dedicated context + returnObjects: true selector overload using const Fn + ReturnType<Fn>, so Target is no longer collapsed to unknown via ApplyTarget. Resolves Problem 1 of #2398 (Problem 2 was already fixed on master). Thanks @​sauravgupta-dotcom (#2438). Fixes #2398.

v26.3.2

• fix: chained formatters with a parenthesised option that contains the format separator (e.g. join(separator: ', ')) now work at any position in the chain, not just first. Previously the comma-in-parens reassembly only repaired formats[0], so {{v, uppercase, join(separator: ', ')}} split the join(...) option on the inner comma and never rejoined it, producing corrupt output. Replaced the first-position-only repair with a position-independent pass that re-joins fragments until each open paren closes. Thanks @​spokodev (#2437).

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; t...

  Description has been truncated

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.