Skip to content

Bump the frontend-npm group in /frontend with 12 updates#171

Merged
helgeklein merged 4 commits into
mainfrom
dependabot/npm_and_yarn/frontend/frontend-npm-2df22b9693
Jul 1, 2026
Merged

Bump the frontend-npm group in /frontend with 12 updates#171
helgeklein merged 4 commits into
mainfrom
dependabot/npm_and_yarn/frontend/frontend-npm-2df22b9693

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 29, 2026

Copy link
Copy Markdown
Contributor

Bumps the frontend-npm group in /frontend with 12 updates:

Package From To
@mui/material 9.1.1 9.1.2
@react-spring/web 10.1.1 10.1.2
@tanstack/react-virtual 3.14.3 3.14.4
axios 1.18.0 1.18.1
i18next 26.3.1 26.3.3
swiper 12.2.0 14.0.0
@biomejs/biome 2.5.0 2.5.1
@playwright/test 1.61.0 1.61.1
@types/node 26.0.0 26.0.1
@vitejs/plugin-react 6.0.2 6.0.3
playwright 1.61.0 1.61.1
vite 8.0.16 8.1.0

Updates @mui/material from 9.1.1 to 9.1.2

Release notes

Sourced from @​mui/material's releases.

v9.1.2

A big thanks to the 5 contributors who made this release possible.

@mui/material@9.1.2

@mui/system@9.1.2

Docs

Core

All contributors of this release in alphabetical order: @​brijeshb42, @​Janpot, @​LukasTy, @​mj12albert, @​siriwatknp

Changelog

Sourced from @​mui/material's changelog.

9.1.2

Jun 23, 2026

A big thanks to the 5 contributors who made this release possible.

@mui/material@9.1.2

@mui/system@9.1.2

Docs

Core

All contributors of this release in alphabetical order: @​brijeshb42, @​Janpot, @​LukasTy, @​mj12albert, @​siriwatknp

Commits

Updates @react-spring/web from 10.1.1 to 10.1.2

Release notes

Sourced from @​react-spring/web's releases.

v10.1.2

Bug Fixes

  • core: PickAnimated now infers all animated keys when a partial from is provided. Previously a from prop collapsed the result type to just the from shape, dropping to keys, forward props, and the other transition phases — so useSpring({ width: 100, height: 100, from: { width: 0 } }) made styles.height a compile error even though height animates at runtime. It now merges from with the to, forward, and transition-phase values. (#2545)
  • core: The SpringValue-level onChange now receives an AnimationResult ({ value, finished: false, cancelled: false }) instead of the raw value, so result.value is no longer undefined mid-animation. This matches onStart/onRest and the Controller-level onChange. The internal change event the animated tree subscribes to still emits the raw value. (#2548)
  • animated: Fixed a cannot add a new property crash when wrapping non-extensible React Native host components. On Hermes, host components like View, Text, and Image become non-extensible after their first render, breaking the wrapper cache. createHost now attempts the direct write first (fast path, unchanged for extensible components) and falls back to a module-level WeakMap when the write is rejected. (#2535)

Performance

  • shared: Improved string interpolation performance with large amounts of data by caching output number parsing in createStringInterpolator. (#2547)

Full Changelog: pmndrs/react-spring@v10.1.1...v10.1.2

Commits
  • 59b1e53 chore: version packages (#2552)
  • 589ee01 fix(core): pass an AnimationResult to SpringValue onChange (#2548)
  • 2c65624 fix: cache output number parsing in createStringInterpolator (#2547)
  • bb37051 fix(core): infer all animated keys when a partial from is provided (#2545)
  • ea94949 fix(animated): WeakMap fallback for non-extensible component caching (#2535)
  • See full diff in compare view

Updates @tanstack/react-virtual from 3.14.3 to 3.14.4

Release notes

Sourced from @​tanstack/react-virtual's releases.

@​tanstack/react-virtual@​3.14.4

Patch Changes

Changelog

Sourced from @​tanstack/react-virtual's changelog.

3.14.4

Patch Changes

Commits

Updates axios from 1.18.0 to 1.18.1

Release notes

Sourced from axios's releases.

v1.18.1 — June 21, 2026

This release focuses on Node HTTP adapter fixes, safer AxiosError serialisation, runtime/type correctness fixes, documentation updates, and dependency maintenance.

🐛 Bug Fixes

  • AxiosError Serialisation: Made AxiosError#cause non-enumerable to prevent circular JSON serialisation failures when errors include nested causes. (#10913)
  • Node HTTP Adapter: Guarded socket.setKeepAlive for proxy agent streams, accepted path-only URLs when socketPath is configured, deferred environment proxy handling to Node, and explicitly passed maxBodyLength through to follow-redirects. (#10917, #10930, #10942, #10993)
  • Runtime and Type Correctness: Fixed several runtime crashes, type definition mismatches, and incorrect error handling paths. (#10959, #11021)
  • AxiosURLSearchParams: Switched the encoder callback to an arrow function so encoder.call(this) receives the AxiosURLSearchParams instance correctly. (#11019)

🔧 Maintenance & Chores

  • Documentation: Documented sensitive headers and status transition behaviour, prepared cleaned-up docs, added Deno install instructions, and clarified that request data is request-specific (#11007, #11010, #11023, #11025)

  • Dependencies: Bumped vite, rollup, form-data, js-yaml, and multer across the root project, docs, smoke tests, and module test workspaces. (#11011, #11012, #11013, #11014, #11015, #11016, #11017, #11026)

🌟 New Contributors

We are thrilled to welcome our new contributors. Thank you for helping improve axios:

Full Changelog

Changelog

Sourced from axios's changelog.

Changelog

Commits
  • a209bfb chore(release): prepare release 1.18.1 (#11027)
  • fa6a55e chore(deps-dev): bump multer from 2.1.1 to 2.2.0 (#11026)
  • 40e7be8 docs: clarifies that request data is request-specific in axios (#11025)
  • a446b39 fix(AxiosURLSearchParams): use arrow function so encoder.call(this) receives ...
  • cf1306a docs: add Deno to install instructions (#11023)
  • b32880a fix: incorrect use of error (#11021)
  • 1792eda fix: ensure maxBodyLength is explicitly passed to follow-redirects (#10993)
  • 30499d6 fix: various runtime crashes and type definition mismatches (#10959)
  • 20ce9c4 fix(http): defer env proxy handling to Node (#10942)
  • e64bcf9 chore(deps): merge branch 'v1.x' into tests/module/cjs (#11014)
  • Additional commits viewable in compare view

Updates i18next from 26.3.1 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).
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).
Commits

Updates swiper from 12.2.0 to 14.0.0

Release notes

Sourced from swiper's releases.

v14.0.0

Swiper v14 is a ground-up TypeScript rewrite of the entire codebase, focused on smaller bundles, more accurate types, and a modern browser baseline. (We skipped v13.)

Upgrading from v12 requires no code changes. Every option, default, event, payload, method signature, and module import (swiper/modules, swiper/react, swiper/vue, swiper/element, …) behaves exactly as before. The only differences you may notice are tighter TypeScript types and a narrower set of supported browsers — see Breaking Changes below.

Highlights

  • Single TypeScript source of truth. src/ is now .ts/.tsx. The hand-maintained .d.ts tree (src/types/, the per-module .d.ts files) is gone — declarations are emitted directly from the runtime source with tsc, so the shipped types can no longer drift from the implementation. Several signatures that used to be any are now correctly typed (e.g. getTranslate(): number).
  • Per-module type augmentation. Each module augments the central Swiper / SwiperOptions / SwiperEvents interfaces. Importing a module (e.g. import { Navigation } from 'swiper/modules') brings its option, method, and event types along with it — mirroring how the runtime already requires registration.
  • More reliable type resolution. Types now resolve correctly under classic node, node16/nodenext, and bundler module resolution, and swiper/bundle exposes every module's options out of the box. Verified by a consumer-simulation test suite.
  • Zero runtime dependencies. The ssr-window dependency was removed and replaced with inline environment guards. Swiper now installs with no transitive runtime deps.
  • Smaller minified bundles. Legacy DOM-compat helpers and below-baseline feature detection were removed. The shared DOM utils shrank ~28%, and the main builds are ~2–4% smaller minified (swiper.min.js −4.1%, swiper-element.min.js −2.9%, swiper-bundle.min.js −2.3%).
  • Babel removed from the build. TypeScript now handles the JSX transform for the React wrapper, and @babel/preset-env is a no-op at the v14 baseline. Runtime output is byte-identical (React output is marginally smaller).

Breaking Changes

  • Browser baseline raised to the last ~2 years of evergreen browsers. Swiper v14 targets Chrome / Edge 110+, Safari 16.4+ (iOS 16.4+), and Firefox 110+. Code paths and feature detection for older browsers were removed (e.g. the smoothScroll support flag, the Safari < 16.2 perspective workaround, and the legacy DocumentTouch touch check). iOS/Android-specific quirk handling is kept but simplified. If you need to support older browsers, stay on v12.
  • Node.js >= 20.19.0 is now required to build/develop against the package (engines was >= 4.7.0). This does not affect the browser runtime.
  • Type-level changes. Stricter types may surface latent issues in code that previously relied on any-typed access to Swiper internals. These are compile-time only — there are no runtime behavior changes.

SSR

ssr-window's mock window/document were replaced with inline typeof guards. Server rendering with the React / Vue / Element wrappers is unaffected — they only instantiate Swiper in client-side mount effects. Imperatively calling new Swiper(...) in a pure Node (non-DOM) environment once again no-ops gracefully, matching v12 behavior, and is now locked down by a dedicated SSR runtime test.

Changelog

Sourced from swiper's changelog.

14.0.0 (2026-06-26)

Swiper v14 is a ground-up TypeScript rewrite of the entire codebase, focused on smaller bundles, more accurate types, and a modern browser baseline. (We skipped v13.)

Upgrading from v12 requires no code changes. Every option, default, event, payload, method signature, and module import (swiper/modules, swiper/react, swiper/vue, swiper/element, …) behaves exactly as before. The only differences you may notice are tighter TypeScript types and a narrower set of supported browsers — see Breaking Changes below.

Highlights

  • Single TypeScript source of truth. src/ is now .ts/.tsx. The hand-maintained .d.ts tree (src/types/, the per-module .d.ts files) is gone — declarations are emitted directly from the runtime source with tsc, so the shipped types can no longer drift from the implementation. Several signatures that used to be any are now correctly typed (e.g. getTranslate(): number).
  • Per-module type augmentation. Each module augments the central Swiper / SwiperOptions / SwiperEvents interfaces. Importing a module (e.g. import { Navigation } from 'swiper/modules') brings its option, method, and event types along with it — mirroring how the runtime already requires registration.
  • More reliable type resolution. Types now resolve correctly under classic node, node16/nodenext, and bundler module resolution, and swiper/bundle exposes every module's options out of the box. Verified by a consumer-simulation test suite.
  • Zero runtime dependencies. The ssr-window dependency was removed and replaced with inline environment guards. Swiper now installs with no transitive runtime deps.
  • Smaller minified bundles. Legacy DOM-compat helpers and below-baseline feature detection were removed. The shared DOM utils shrank ~28%, and the main builds are ~2–4% smaller minified (swiper.min.js −4.1%, swiper-element.min.js −2.9%, swiper-bundle.min.js −2.3%).
  • Babel removed from the build. TypeScript now handles the JSX transform for the React wrapper, and @babel/preset-env is a no-op at the v14 baseline. Runtime output is byte-identical (React output is marginally smaller).

Breaking Changes

  • Browser baseline raised to the last ~2 years of evergreen browsers. Swiper v14 targets Chrome / Edge 110+, Safari 16.4+ (iOS 16.4+), and Firefox 110+. Code paths and feature detection for older browsers were removed (e.g. the smoothScroll support flag, the Safari < 16.2 perspective workaround, and the legacy DocumentTouch touch check). iOS/Android-specific quirk handling is kept but simplified. If you need to support older browsers, stay on v12.
  • Node.js >= 20.19.0 is now required to build/develop against the package (engines was >= 4.7.0). This does not affect the browser runtime.
  • Type-level changes. Stricter types may surface latent issues in code that previously relied on any-typed access to Swiper internals. These are compile-time only — there are no runtime behavior changes.

SSR

ssr-window's mock window/document were replaced with inline typeof guards. Server rendering with the React / Vue / Element wrappers is unaffected — they only instantiate Swiper in client-side mount effects. Imperatively calling new Swiper(...) in a pure Node (non-DOM) environment once again no-ops gracefully, matching v12 behavior, and is now locked down by a dedicated SSR runtime test.

Commits
  • 900ec1a 14.0.0
  • 38153db docs(v14): record Phase 8 SSR runtime parity work
  • 45c664d test(v14): add SSR runtime smoke test
  • edfc6bb fix(v14): guard instantiation path for non-DOM (SSR) environments
  • b38192e Merge branch 'master' into v14
  • a824a75 14.0.0-beta.2
  • 119c3e2 docs(v14): note swiper/bundle types fix in plan
  • ea70e59 test(v14): cover swiper/bundle module options in consumer types
  • 8e5d26f fix(v14): expose module options on swiper/bundle types
  • 8fe7128 14.0.0-beta.1
  • Additional commits viewable in compare view

Updates @biomejs/biome from 2.5.0 to 2.5.1

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.5.1

2.5.1

Patch Changes

  • #10722 f8a303d Thanks @​denbezrukov! - Fixed CSS formatter output for comments between import media queries.

    -@import url("print.css") print,
-/* comment */
-screen;
+@import url("print.css") print, /* comment */ screen;

  • #10738 9fdc560 Thanks @​JamBalaya56562! - Fixed #9899: the json and json-pretty reporters now escape backslashes in a diagnostic's location.path. Previously, paths containing backslashes (such as Windows-style paths) were emitted unescaped, producing invalid JSON.

    -    "path": "src\account\setup-passkey.tsx",
+    "path": "src\\account\\setup-passkey.tsx",

  • #10626 5f837df Thanks @​tom-groves! - Fixed #10625: biome migrate no longer emits an invalid trailing comma when a renamed rule (such as noConsoleLog → noConsole) is the last member of its rule group. Previously this produced malformed output that aborted the migration of a strict-JSON biome.json with a parsing error.

  • #10535 c245f9d Thanks @​Mokto! - Fixed a false positive in noUnusedVariables for Svelte files where variables referenced inside {@html expr} blocks were incorrectly reported as unused.

  • #10668 a0f197e Thanks @​Netail! - The biome init command has been updated to include a more up-to-date URL to the first-party extensions page.

  • #10667 d8c3e87 Thanks @​Netail! - Fixed #10664: useErrorCause now correctly detects a shorthand property.

  • #10696 ef2373f Thanks @​ematipico! - Fixed #9566. Improved how the Biome Language Server loads multiple configuration files inside a workspace.

  • #10705 4ccb410 Thanks @​ematipico! - Fixed #10652. Biome plugins are now properly filtered when using --only and --skip flags.

  • #10669 aa0a6eb Thanks @​Netail! - Fixed #10651: useInlineScriptId now correctly trims trivia to detect if an id attribute has been set.

  • #10689 844b1be Thanks @​ematipico! - Fixed #10658. The issue was caused by the "Go-to definition" editor feature, which was enabled by default. The feature is now disabled by default. To work, the feature triggers the scanner to build the module graph. This caused memory leak issues in cases where Biome starts in the home directory to modify files.

    If you relied on this new feature, you must now turn on using the [editor settings] of the extension e.g. Zed and VSCode.

  • #10695 043fbb5 Thanks @​ematipico! - Fixed #10674. Biome now throws an error when the field level is missing from a rule option.

  • #10712 5941df2 Thanks @​Conaclos! - Improved the diagnostic and the documentation of useFlatMap.

  • #10615 23814f1 Thanks @​qwertycxz! - Improved the DX the JSON schema when it's used by certain code editors like VSCode.

  • #10688 ec69489 Thanks @​ematipico! - Fixed a bug where the Biome Daemon did not correctly shut down when the editor was closed during an in-progress operation, especially while scanning.

  • #10701 6c2e0d7 Thanks @​ematipico! - Fixed #10694. The Biome Language Server no longer prints an error when the user hovers a variable imported from node_modules.

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.5.1

Patch Changes

  • #10722 f8a303d Thanks @​denbezrukov! - Fixed CSS formatter output for comments between import media queries.

    -@import url("print.css") print,
-/* comment */
-screen;
+@import url("print.css") print, /* comment */ screen;

  • #10738 9fdc560 Thanks @​JamBalaya56562! - Fixed #9899: the json and json-pretty reporters now escape backslashes in a diagnostic's location.path. Previously, paths containing backslashes (such as Windows-style paths) were emitted unescaped, producing invalid JSON.

    -    "path": "src\account\setup-passkey.tsx",
+    "path": "src\\account\\setup-passkey.tsx",

  • #10626 5f837df Thanks @​tom-groves! - Fixed #10625: biome migrate no longer emits an invalid trailing comma when a renamed rule (such as noConsoleLog → noConsole) is the last member of its rule group. Previously this produced malformed output that aborted the migration of a strict-JSON biome.json with a parsing error.

  • #10535 c245f9d Thanks @​Mokto! - Fixed a false positive in noUnusedVariables for Svelte files where variables referenced inside {@html expr} blocks were incorrectly reported as unused.

  • #10668 a0f197e Thanks @​Netail! - The biome init command has been updated to include a more up-to-date URL to the first-party extensions page.

  • #10667 d8c3e87 Thanks @​Netail! - Fixed #10664: useErrorCause now correctly detects a shorthand property.

  • #10696 ef2373f Thanks @​ematipico! - Fixed #9566. Improved how the Biome Language Server loads multiple configuration files inside a workspace.

  • #10705 4ccb410 Thanks @​ematipico! - Fixed #10652. Biome plugins are now properly filtered when using --only and --skip flags.

  • #10669 aa0a6eb Thanks @​Netail! - Fixed #10651: useInlineScriptId now correctly trims trivia to detect if an id attribute has been set.

  • #10689 844b1be Thanks @​ematipico! - Fixed #10658. The issue was caused by the "Go-to definition" editor feature, which was enabled by default. The feature is now disabled by default. To work, the feature triggers the scanner to build the module graph. This caused memory leak issues in cases where Biome starts in the home directory to modify files.

    If you relied on this new feature, you must now turn on using the [editor settings] of the extension e.g. Zed and VSCode.

  • #10695 043fbb5 Thanks @​ematipico! - Fixed #10674. Biome now throws an error when the field level is missing from a rule option.

  • #10712 5941df2 Thanks @​Conaclos! - Improved the diagnostic and the documentation of useFlatMap.

  • #10615 23814f1 Thanks @​qwertycxz! - Improved the DX the JSON schema when it's used by certain code editors like VSCode.

  • #10688 ec69489 Thanks @​ematipico! - Fixed a bug where the Biome Daemon did not correctly shut down when the editor was closed during an in-progress operation, especially while scanning.

  • #10701 6c2e0d7 Thanks @​ematipico! - Fixed #10694. The Biome Language Server no longer prints an error when the user hovers a variable imported from node_modules.

  • #10681 888515b Thanks @​Conaclos! - Fixed useExportType that reported useless details in some diagnostics.

... (truncated)

Commits

Updates @playwright/test from 1.61.0 to 1.61.1

Release notes

Sourced from @​playwright/test's releases.

v1.61.1

Bug Fixes

  • #41365 [Bug]: Expect.Extend matcher with same name as default matcher in same expect instance overrides default matchers implementation to custom matcher
  • #41351 [Bug]: Playwright UI mode: apiRequestContext._wrapApiCall reports unexpected number of bytes (same test passes in headed mode)
  • #41360 [Bug]: Trace viewer: message times in websockets are downscaled by 1000
  • #41311 [Bug]: [Regression]: Sync loader throws "context.conditions?.includes is not a function" on Node 22.15
  • #41371 [Regression]: Sync ESM loader (registerHooks) fails to resolve extensionless .ts subpath imports across pnpm workspace symlinks
Commits
  • 39e3553 cherry-pick(#41399): fix(test): load require-reached files as commonjs in syn...
  • 4328122 chore: mark v1.61.1 (#41404)
  • 2c29a94 fix(tracing): stop recording websocket frames outside of chunks (#41398)
  • 4324b19 cherry-pick(#41367): fix(test): keep builtin expect matchers on base extend
  • 041e7e3 cherry-pick(#41364): fix(har): WebSocket message timestamps should be in mi...
  • b8a0fc3 cherry-pick(#41309, #43149): Revert "fix(firefox): treat `navigationCommitted...
  • b5a3175 cherry-pick(#41319): fix(loader): support other node versions
  • d4724a9 cherry-pick(#41290): feat(docker): add Ubuntu 26.04 (Resolute Raccoon) image
  • See full diff in compare view

Updates @types/node from 26.0.0 to 26.0.1

Commits

Updates @vitejs/plugin-react from 6.0.2 to 6.0.3

Changelog

Sourced from @​vitejs/plugin-react's changelog.

6.0.3 (2026-06-23)

Commits
  • 640fd35 release: plugin-react@6.0.3
  • 889efb0 fix(deps): update all non-major dependencies (#1249)
  • 6c57dd4 fix(plugin-react): use '/' base in bundledDev preamble to fix non-root base p...
  • 3cc33a7 fix(deps): update react-related dependencies (#1245)
  • c0f7c7f docs: mention the Biome rule in the "Consistent components exports" section (...
  • cd80f0f fix(deps): update all non-major dependencies (#1241)
  • e38acca fix(deps): update all non-majo...

    Description has been truncated

@dependabot
Bump the frontend-npm group in /frontend with 12 updates
90072a3 
Bumps the frontend-npm group in /frontend with 12 updates:

| Package | From | To |
| --- | --- | --- |
| [@mui/material](https://github.com/mui/material-ui/tree/HEAD/packages/mui-material) | `9.1.1` | `9.1.2` |
| [@react-spring/web](https://github.com/pmndrs/react-spring) | `10.1.1` | `10.1.2` |
| [@tanstack/react-virtual](https://github.com/TanStack/virtual/tree/HEAD/packages/react-virtual) | `3.14.3` | `3.14.4` |
| [axios](https://github.com/axios/axios) | `1.18.0` | `1.18.1` |
| [i18next](https://github.com/i18next/i18next) | `26.3.1` | `26.3.3` |
| [swiper](https://github.com/nolimits4web/Swiper) | `12.2.0` | `14.0.0` |
| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | `2.5.0` | `2.5.1` |
| [@playwright/test](https://github.com/microsoft/playwright) | `1.61.0` | `1.61.1` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `26.0.0` | `26.0.1` |
| [@vitejs/plugin-react](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react) | `6.0.2` | `6.0.3` |
| [playwright](https://github.com/microsoft/playwright) | `1.61.0` | `1.61.1` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `8.0.16` | `8.1.0` |


Updates `@mui/material` from 9.1.1 to 9.1.2
- [Release notes](https://github.com/mui/material-ui/releases)
- [Changelog](https://github.com/mui/material-ui/blob/master/CHANGELOG.md)
- [Commits](https://github.com/mui/material-ui/commits/v9.1.2/packages/mui-material)

Updates `@react-spring/web` from 10.1.1 to 10.1.2
- [Release notes](https://github.com/pmndrs/react-spring/releases)
- [Commits](https://github.com/pmndrs/react-spring/compare/@react-spring/web@10.1.1...@react-spring/web@10.1.2)

Updates `@tanstack/react-virtual` from 3.14.3 to 3.14.4
- [Release notes](https://github.com/TanStack/virtual/releases)
- [Changelog](https://github.com/TanStack/virtual/blob/main/packages/react-virtual/CHANGELOG.md)
- [Commits](https://github.com/TanStack/virtual/commits/@tanstack/react-virtual@3.14.4/packages/react-virtual)

Updates `axios` from 1.18.0 to 1.18.1
- [Release notes](https://github.com/axios/axios/releases)
- [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md)
- [Commits](axios/axios@v1.18.0...v1.18.1)

Updates `i18next` from 26.3.1 to 26.3.3
- [Release notes](https://github.com/i18next/i18next/releases)
- [Changelog](https://github.com/i18next/i18next/blob/master/CHANGELOG.md)
- [Commits](i18next/i18next@v26.3.1...v26.3.3)

Updates `swiper` from 12.2.0 to 14.0.0
- [Release notes](https://github.com/nolimits4web/Swiper/releases)
- [Changelog](https://github.com/nolimits4web/swiper/blob/v14.0.0/CHANGELOG.md)
- [Commits](nolimits4web/swiper@v12.2.0...v14.0.0)

Updates `@biomejs/biome` from 2.5.0 to 2.5.1
- [Release notes](https://github.com/biomejs/biome/releases)
- [Changelog](https://github.com/biomejs/biome/blob/main/packages/@biomejs/biome/CHANGELOG.md)
- [Commits](https://github.com/biomejs/biome/commits/@biomejs/biome@2.5.1/packages/@biomejs/biome)

Updates `@playwright/test` from 1.61.0 to 1.61.1
- [Release notes](https://github.com/microsoft/playwright/releases)
- [Commits](microsoft/playwright@v1.61.0...v1.61.1)

Updates `@types/node` from 26.0.0 to 26.0.1
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `@vitejs/plugin-react` from 6.0.2 to 6.0.3
- [Release notes](https://github.com/vitejs/vite-plugin-react/releases)
- [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite-plugin-react/commits/plugin-react@6.0.3/packages/plugin-react)

Updates `playwright` from 1.61.0 to 1.61.1
- [Release notes](https://github.com/microsoft/playwright/releases)
- [Commits](microsoft/playwright@v1.61.0...v1.61.1)

Updates `vite` from 8.0.16 to 8.1.0
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/create-vite@8.1.0/packages/vite)

---
updated-dependencies:
- dependency-name: "@mui/material"
  dependency-version: 9.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-npm
- dependency-name: "@react-spring/web"
  dependency-version: 10.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-npm
- dependency-name: "@tanstack/react-virtual"
  dependency-version: 3.14.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-npm
- dependency-name: axios
  dependency-version: 1.18.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-npm
- dependency-name: i18next
  dependency-version: 26.3.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: frontend-npm
- dependency-name: swiper
  dependency-version: 14.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: frontend-npm
- dependency-name: "@biomejs/biome"
  dependency-version: 2.5.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: frontend-npm
- dependency-name: "@playwright/test"
  dependency-version: 1.61.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: frontend-npm
- dependency-name: "@types/node"
  dependency-version: 26.0.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: frontend-npm
- dependency-name: "@vitejs/plugin-react"
  dependency-version: 6.0.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: frontend-npm
- dependency-name: playwright
  dependency-version: 1.61.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: frontend-npm
- dependency-name: vite
  dependency-version: 8.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: frontend-npm
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Dependency update and supply-chain maintenance work. frontend Changes affecting the frontend application or dependencies. labels Jun 29, 2026
@helgeklein helgeklein merged commit 752c4a2 into main Jul 1, 2026
17 checks passed
@helgeklein helgeklein deleted the dependabot/npm_and_yarn/frontend/frontend-npm-2df22b9693 branch July 1, 2026 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Dependency update and supply-chain maintenance work. frontend Changes affecting the frontend application or dependencies.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@helgeklein