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

[dependabot]

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

Package	From	To
i18next	26.2.0	26.3.1
mediabunny	1.45.3	1.46.0
react	19.2.6	19.2.7
react-dom	19.2.6	19.2.7
react-router-dom	7.15.1	7.17.0
swiper	12.1.4	12.2.0
zustand	5.0.13	5.0.14

Updates i18next from 26.2.0 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.

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.

Commits

• 7bdb5d7 26.3.1
• a655e32 changelog: 26.3.1 entry for #2436
• 57ed812 fix(types): keyPrefix no longer pollutes t() return type with sibling keys (#...
• bdf651c 26.3.0
• 988a362 changelog: 26.3.0 entry for #2434
• 159506c feat(types): introduce ResourceNamespaceMap for monorepo namespace augmentati...
• df68b1f ci: restore JSR publishing via GitHub Actions OIDC
• See full diff in compare view

Updates mediabunny from 1.45.3 to 1.46.0

Release notes

Sourced from mediabunny's releases.

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

• b4e5107 Bump minor
• c423d62 Change keyFrame parameter priority
• 0cdf006 Add VideoSample.encodeOptions, optimized ArrayBuffer-backed VideoSample cloning
• bb2f5d5 Clarify and better error messages
• ebfb1e6 Add MediabunnyServerOptions and configurable hardware context (closes #389)
• 8fbd318 Bump patch
• d92df80 Change requestEntireFile() slice offset logic (#390)
• 6832153 Merge branch 'main' of https://github.com/Vanilagy/metamuxer
• 82690ef Clean up AVC packet NALUs with AUD in them for Chromium key frame detection (...
• c0d93f4 Support QuickTime nclc color information (#397)
• 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)

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)

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

Changelog

Sourced from react-router-dom's changelog.

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

• 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 swiper from 12.1.4 to 12.2.0

Release notes

Sourced from swiper's releases.

v12.2.0

Bug Fixes

• avoid duplicate css type resolutions (aaf6014)
• core: guard against stale event listeners in onTouchEnd and onTouchMove (00fe610)
• core: guard all event handlers against stale invocations on destroyed swiper (3b2b85f)
• types: support boolean as controller type (b10f9e0)

Changelog

Sourced from swiper's changelog.

12.2.0 (2026-05-27)

Bug Fixes

• avoid duplicate css type resolutions (aaf6014)
• core: guard against stale event listeners in onTouchEnd and onTouchMove (00fe610)
• core: guard all event handlers against stale invocations on destroyed swiper (3b2b85f)
• types: support boolean as controller type (b10f9e0)

Commits

• 929c014 12.2.0
• 157784e chore: sponsors
• 0348bc9 chore: remove lock/stale
• edf0984 chore: delete workflows
• 3b2b85f fix(core): guard all event handlers against stale invocations on destroyed sw...
• b986149 Merge pull request #8183 from arturovt/fix/guard-stale-listener
• 43c24f1 Clean up comment in onTouchMove function
• ac272bf Remove stale listener comment in onTouchEnd
• 7a5ae86 Merge pull request #8186 from Stanzilla/fix/css-types-no-duplicates
• 832b84b Merge pull request #8188 from evanclan/fix/controller-boolean-type
• Additional commits viewable 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]

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