build(deps): bump the production-dependencies group across 1 directory with 6 updates

[dependabot]

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

Package	From	To
i18next	26.2.0	26.3.3
mediabunny	1.45.3	1.49.0
react	19.2.6	19.2.7
react-dom	19.2.6	19.2.7
react-router-dom	7.15.1	7.18.1
zustand	5.0.13	5.0.14

Updates i18next from 26.2.0 to 26.3.3

Release notes

Sourced from i18next's releases.

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.

Changelog

Sourced from i18next's changelog.

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

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

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.

Commits

• cf7080d 26.3.3
• 05fd7be build
• cc0bd80 changelog: 26.3.3 entry for #2438
• 9cbfa63 fix(types): preserve selector returnObjects shape with context (#2438)
• 3b04712 26.3.2
• fc20f5d changelog: 26.3.2 entry for #2437
• 6901e04 fix: reassemble comma-in-parens formatters at any chain position (#2437)
• 6e08628 README: mention npx i18next-cli localize as the zero-to-localized path
• 7bdb5d7 26.3.1
• a655e32 changelog: 26.3.1 entry for #2436
• Additional commits viewable in compare view

Updates mediabunny from 1.45.3 to 1.49.0

Release notes

Sourced from mediabunny's releases.

v1.49.0

• Added a new Logging singleton that can be used to control the log level of Mediabunny. Great for silencing console output for CLI applications. (#415)
• Added ID3v2 read support for FLAC files (#417)
• Removed forgotten console.log in range request warning path

v1.48.1

• Fixed AVC/HEVC packet segmentation for MPEG-TS when no AUDs are present (#414)
• Fixed MPEG-TS metadata reading taking unnecessarily long sometimes

v1.48.0

• Added InputFormatOptions.hls.offsetTimestampsByDateTime (defaults to true), allowing you to disable Mediabunny offsetting timestamps by date time metadata found in HLS playlists
• Added the ability to configure decoder preferences like hardware acceleration for each video sink (#406)
• Fixed HLS request resolution logic not properly handling redirects
• Improved error handling after disposing of an Input (#405)
• Fixed occassional assertion failures when reading files with high contention (#404)

v1.47.0

• Added AudioSample.trim() for getting a slice of an existing audio sample
• Fixed zero-sample ISOBMFF fragments throwing an error (#411)
• Fixed unhandled rejection when disposing invalid input (#413)
• Fixed process in Conversion API being called before other transformations, not after (#403)

v1.46.0

• Added options to registerMediabunnyServer, allowing you to specify a custom hardware context (#389)
• Added VideoSample.encodeOptions and VideoSample.setEncodeOptions() for providing per-frame encoding settings
• keyFrame encoding option now always takes precedence over keyFrameInterval when defined
• Improved VideoSample error messages when the environment has insufficient canvas support
• Improved VideoSample.clone() performance for ArrayBuffer-backed samples

v1.45.5

• Fixed @mediabunny/server memory leaks (#392)
• Made sure that at least one track per type is enabled when muxing ISOBMFF (#391)
• Added support for reading and writing QuickTime nclc color space information (#397)
• Added workaround for faulty Chromium key frame detection causing VideoDecoder error (#396)
• UrlSource now properly respects the Range header passed into requestInit
• Improved requestInit docs for UrlSource (#387)

v1.45.4

• StreamSource is now called CustomSource. StreamSource still exists as a deprecated alias.
• Improved MP3 frame boundary recovery for broken files (#382)
• Fixed Date instances with incorrect timezone being emitted by some ID3 tags
• Fixed FinalizationRegistry causing Input memory leaks when used with CustomSource (#367)

Commits

• 3e68665 Bump minor
• cdc2ef6 Add Logging singleton to manually control Mediabunny's console output (fixes ...
• 92a384f Added ID3v2 support for FLAC files. (Fixes #417) (#418)
• 5b890ef Dumb oversight
• 7f96336 Bump patch
• bfd4059 Add advanced access unit delimination logic to MPEG-TS demuxer (fixes #414), ...
• 53833f6 Add missing validation for HlsInputFormatOptions
• 794c97b Bump minor
• 5b4a5db Add HlsInputFormatOptions.offsetTimestampsByDateTime option, add InputTrack.g...
• 2f0c040 Properly handle subrequests for redirected URLs
• Additional commits viewable in compare view

Updates react from 19.2.6 to 19.2.7

Release notes

Sourced from react's releases.

19.2.7 (June 1st, 2026)

React Server Components

• Fixed missing FormData entries in Server Actions which regressed in 19.2.6 (#36566 by @​unstubbable)

Changelog

Sourced from react's changelog.

19.2.7 (June 1, 2026)

React Server Components

• Fixed missing FormData entries in Server Actions which regressed in 19.2.6 (@​unstubbable #36566)

Commits

• 6117d7c Version 19.2.7 (#36591)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react since your current version.

Updates react-dom from 19.2.6 to 19.2.7

Release notes

Sourced from react-dom's releases.

19.2.7 (June 1st, 2026)

React Server Components

• Fixed missing FormData entries in Server Actions which regressed in 19.2.6 (#36566 by @​unstubbable)

Changelog

Sourced from react-dom's changelog.

19.2.7 (June 1, 2026)

React Server Components

• Fixed missing FormData entries in Server Actions which regressed in 19.2.6 (@​unstubbable #36566)

Commits

• 6117d7c Version 19.2.7 (#36591)
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for react-dom since your current version.

Updates react-router-dom from 7.15.1 to 7.18.1

Changelog

Sourced from react-router-dom's changelog.

v7.18.1

Patch Changes

• Fix incorrect package.json main field for CommonJS builds (#15238)
• Updated dependencies:
  • react-router@7.18.1

v7.18.0

Patch Changes

• Updated dependencies:
  • react-router@7.18.0

v7.17.0

Patch Changes

• Updated dependencies:
  • react-router@7.17.0

v7.16.0

Patch Changes

• Remove stale/invalid unpkg field from package.json. This was removed from other packages with the release of v7 but missed in the react-router-dom re-export package (#15075)
• Updated dependencies:
  • react-router@7.16.0

Commits

• afdf85d Release v7.18.1 (#15253)
• 2ecaa1d Fix react-router-dom main entry metadata (#15238)
• 6fb1e79 Release v7.18.0 (#15187)
• 195a0d0 Release v7.17.0 (#15145)
• 8984d23 Release v7.16.0 (#15105)
• 3ed77af chore: format
• e96962b fix: remove stale unpkg field from react-router-dom (#15075)
• See full diff in compare view

Updates zustand from 5.0.13 to 5.0.14

Release notes

Sourced from zustand's releases.

v5.0.14

This release fixes a type issue in devtools.

What's Changed

• fix(devtools): improve type inference for Devtools initializer by @​dbritto-dev in pmndrs/zustand#3511

New Contributors

• @​TheSeydiCharyyev made their first contribution in pmndrs/zustand#3487
• @​brofrong made their first contribution in pmndrs/zustand#3496
• @​hyun907 made their first contribution in pmndrs/zustand#3506

Full Changelog: pmndrs/zustand@v5.0.13...v5.0.14

Commits

• bfb2a9e 5.0.14
• 62b2aff chore(deps): update dev dependencies (#3513)
• ad77bd3 fix(devtools): improve type inference for Devtools initializer (#3511)
• 8476d2c update pnpm etc (#3512)
• d690ec2 docs(combine): add object constraints to T and U in signature (#3506)
• fd8c601 docs(react): add Action constraint to redux middleware signature (#3492)
• 2ce8226 docs(immer): fix setPerson updater type in usage examples (#3502)
• 038b938 docs(updating-state): use curried create form with explicit state type (#3503)
• 60a91b4 docs(devtools): add missing devtools import to troubleshooting example (#3501)
• efad169 Update FUNDING.json
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions