Skip to content

Bump the npm-minor-patch group across 1 directory with 8 updates - #27

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/frontend/npm-minor-patch-3f5166de16
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/frontend/npm-minor-patch-3f5166de16

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

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

Package From To
@solidjs/router 1.0.0 1.0.1
solid-js 1.9.15 1.9.18
@axe-core/playwright 4.13.0 4.14.0
@biomejs/biome 2.5.15 2.6.6
@playwright/test 1.63.0 1.65.0
vite 8.3.2 8.3.6
vite-plugin-solid 2.11.14 2.11.15
vitest 5.0.3 5.1.0

Updates @solidjs/router from 1.0.0 to 1.0.1

Release notes

Sourced from @​solidjs/router's releases.

v1.0.1

Patch Changes

  • eaafba6: Stamp history depth from the current entry instead of history.length, so useBeforeLeave and scroll restoration keep working on Back once the browser's session history is full (#694)

  • c3cbd67: Throw a descriptive error in development when an action is called directly instead of through useAction.

  • 473c270: Anchor click handling no longer intercepts links with a non-http(s) scheme (blob:, mailto:, tel:, data:, …). Previously blob: links could be wrongly routed because they inherit the page origin and bypassed the same-origin check.

  • 5a46ba1: Speed up <A> server rendering by roughly 5x

    <A> spent most of its server render time in mergeProps and splitProps, which build accessor-backed prop objects that can never be observed during a one shot renderToString. The default activeClass / inactiveClass merge is gone, the location.pathname normalization is shared instead of repeated per link, JSON.stringify is skipped when there is no state, and on the server a link that passes nothing beyond the props <A> consumes itself now skips splitProps and the JSX spread entirely.

    Rendered output is unchanged on the client, and unchanged on the server apart from the link marker serializing as link rather than link="true" on that fast path. Client bundles get slightly smaller, since the server branch is constant folded away.

  • 65f9ee7: Fixes browser history navigation when Forward is pressed while a Back transition is waiting on route data.

Changelog

Sourced from @​solidjs/router's changelog.

1.0.1

Patch Changes

  • eaafba6: Stamp history depth from the current entry instead of history.length, so useBeforeLeave and scroll restoration keep working on Back once the browser's session history is full (#694)

  • c3cbd67: Throw a descriptive error in development when an action is called directly instead of through useAction.

  • 473c270: Anchor click handling no longer intercepts links with a non-http(s) scheme (blob:, mailto:, tel:, data:, …). Previously blob: links could be wrongly routed because they inherit the page origin and bypassed the same-origin check.

  • 5a46ba1: Speed up <A> server rendering by roughly 5x

    <A> spent most of its server render time in mergeProps and splitProps, which build accessor-backed prop objects that can never be observed during a one shot renderToString. The default activeClass / inactiveClass merge is gone, the location.pathname normalization is shared instead of repeated per link, JSON.stringify is skipped when there is no state, and on the server a link that passes nothing beyond the props <A> consumes itself now skips splitProps and the JSX spread entirely.

    Rendered output is unchanged on the client, and unchanged on the server apart from the link marker serializing as link rather than link="true" on that fast path. Client bundles get slightly smaller, since the server branch is constant folded away.

  • 65f9ee7: Fixes browser history navigation when Forward is pressed while a Back transition is waiting on route data.

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​solidjs/router since your current version.


Updates solid-js from 1.9.15 to 1.9.18

Commits

Updates @axe-core/playwright from 4.13.0 to 4.14.0

Release notes

Sourced from @​axe-core/playwright's releases.

Release 4.14.0

What's Changed

New Contributors

Full Changelog: dequelabs/axe-core-npm@v4.13.0...v4.14.0

Changelog

Sourced from @​axe-core/playwright's changelog.

4.14.0 (2026-10-06)

Bug Fixes

Features

Commits
Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.


Updates @biomejs/biome from 2.5.15 to 2.6.6

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.6.6

2.6.6

Patch Changes

  • #12887 da0422e Thanks @​dyc3! - Added the new nursery rule noArrayMethodsOnArguments. It reports calls to array methods on the arguments object, which isn't an array, so these calls throw a TypeError when the code runs.

    function sum() {
      return arguments.reduce((total, value) => total + value, 0);
    }
  • #12877 cd9e10f Thanks @​dyc3! - Added the nursery rule noConstantComparisons, which reports && and || conditions that can never be true, are always true, or contain a check with no effect.

    if (statusCode <= 400 && statusCode > 500) {}
  • #12876 a7c9586 Thanks @​dyc3! - Added the nursery rule noErasingOperation, which disallows operations with 0 that always result in zero: multiplying by 0, a bitwise AND with 0, and dividing 0 by a number. The other value in these operations has no effect on the result, which usually means the code has a mistake.

    const total = price * 0;
  • #12841 e954f55 Thanks @​dyc3! - Added the nursery rule noNegatedArrayPredicate, which reports negated calls to Array#some() and Array#every() and suggests moving the negation into the callback function.

    // Invalid: use `array.every((item) => !isUnicorn(item))` instead.
    const isMissing = !array.some((item) => isUnicorn(item));
  • #12888 15039f7 Thanks @​dyc3! - Added the new nursery rule noNumberArgumentOutOfRange, which reports number literal arguments of toString(), toFixed(), toExponential() and toPrecision() that are outside the range the method accepts. These calls throw a RangeError at runtime.

    value.toString(64);
  • #12889 1cd7520 Thanks @​dyc3! - Added the nursery rule noSharedBranchCode, which reports code that is repeated at the start or end of every branch of an if statement. That code runs no matter which branch is taken, so it can be moved before or after the if statement.

    if (condition) {
      doSomething();
      cleanup();
    } else {
      doSomethingElse();
      cleanup();
    }

... (truncated)

Commits

Updates @playwright/test from 1.63.0 to 1.65.0

Release notes

Sourced from @​playwright/test's releases.

v1.65.0

🥟 Run tests with Bun

The test runner now runs under Bun. Bun transpiles your TypeScript test files itself, so Playwright does not use Babel or its compilation cache. Pass the --bun flag, because without it bunx playwright test runs on Node.js:

bunx --bun playwright test

Our CI runs the test runner tests under Bun 1.4.3 on Linux. Some features work differently under Bun:

  • There is no watch mode. UI mode does not run tests again when files change, and --only-changed does not follow imports.
  • Bun loads modules itself, so --tsconfig and the JSX options in tsconfig.json have no effect, and custom ESM loaders are not supported.
  • Stack traces do not include async frames, and API names do not include the class name: click instead of locator.click. This changes some step locations, step titles and error messages.
  • Console output of a test does not get into the trace and UI mode.

🚨 Reports with only failures

New failures reporter prints failures and successful retries as they occur, followed by a summary, without progress output.

New onlyFailures option of the HTML, JSON and JUnit reporters keeps only tests with unexpected outcomes, flaky tests and interrupted tests:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
reporter: [
['failures'],
['html', { onlyFailures: true }],
],
});

🎯 Test runner

  • New built-in -exclusive- test lock runs a test only when no other tests are running. All other tests continue to run in parallel with each other:

    test('restart the server', { lock: '-exclusive-' }, async () => {
      // No other test runs while this one is running.
    });
  • test.skip(), test.fixme(), test.fail() and test.slow() now accept only a description. It is recorded in the test annotation:

    test('upload a file', async ({ page }) => {
      test.skip('Not implemented yet');
    });

... (truncated)

Commits
  • a1f35e1 chore: mark v1.65.0 (#43925)
  • a99c1ab cherry-pick(#43918): Revert "fix(docker): use latest stable Chrome for Testin...
  • 6f9a7f5 cherry-pick(#43914): docs(release-notes): update Chromium version for 1.65
  • daf93bb cherry-pick(#43912): feat(chromium): roll to r1254
  • 6545e89 cherry-pick(#43902): chore(deps): bump runtime deps
  • 0347448 fix(test runner): track shared ESM dependencies for only-changed (#43837)
  • 86e6924 fix(clock): cancel real-time timer when replay ends paused (#43873)
  • d745ae0 fix(route): wait for all active handlers before disabling interception (#43889)
  • 6e3f5ff docs: release notes for v1.65 (#43874)
  • aa33d27 fix(chromium): honor Linux config directories for channel connections (#43884)
  • Additional commits viewable in compare view

Updates vite from 8.3.2 to 8.3.6

Release notes

Sourced from vite's releases.

v8.3.6

Bug Fixes

  • await overlapping plugin container close calls (#23935) (175bbeb)
  • build: resolve dynamic imports with queries appended when collecting CSS dependencies (#23909) (df36558)
  • build: use stable module ids in chunk import map hash signatures (fix #23975) (#23976) (8069835)
  • bundled-dev: allow named imports from Node built-ins (#23858) (4260c75)
  • bundled-dev: reload when hmr cannot run an entry again (#23849) (a236886)
  • deps: update @rollup/plugin-alias to v6.0.1 (#23862) (67c965b)
  • deps: update all non-major dependencies (#23896) (46b91c5)
  • deps: update all non-major dependencies (#23966) (b3cb057)
  • deps: update rolldown-related dependencies (#23868) (a63eb87)
  • deps: update rolldown-related dependencies (#23967) (0105733)
  • dev: escape ANSI escape sequence for server.forwardConsole (#23933) (4f340fd)
  • html: remove adjacent module tags on the first line (#23823) (eab1dc2)
  • ignore pnpm's .modules.yaml as a Vite Task input (#23634) (95c2daf)
  • optimizer: detect cache dir precisely (#23912) (cc9bc21)
  • optimizer: resolve subpath imports (#) with Vite's resolver (#23959) (0fdd81e)
  • respect build.sourcemap from environment (#23879) (82e7aa0)
  • server: escape HTML attributes (#23995) (a270391)
  • server: preserve $ patterns in static alias replacements (#23703) (1b6ed05)
  • ssr: convert external require against built-in modules to import for ssr.target=webworker (#23759) (a711f1c)
  • use top-level input for SSR build when build.ssr: true (#23898) (90bc034)
  • wasm: reject .wasm outside server.fs (#23914) (64e2467)
  • watch files that have a query or hash referenced with new URL(..., import.meta.url) (#23780) (e954a9c)
  • worker: keep chunks conflicted with unused workers that are still used by a live worker (#23956) (7139ef3)

Performance Improvements

Miscellaneous Chores

Build System

  • generate sourcemaps in import-meta-current-dirname plugin (#23904) (20d355a)

v8.3.5

Bug Fixes

  • build: handle missing chunk import maps (#23777) (8d7623d)
  • build: include preload dependencies to chunk import map hashing (#23793) (4d16e7c)
  • bundled-dev: apply server.origin to asset URLs (#23683) (52ba877)
  • bundled-dev: declare utf-8 charset in fallback page (#23846) (197daf6)
  • bundled-dev: ignore build.chunkImportMap (#23685) (cfe917d)
  • bundled-dev: include user import.meta.env.* defines in the import.meta.env object (#23713) (6019aa7)
  • bundled-dev: map forwarded error stacks through the bundle source maps (#23741) (11fe1e4)

... (truncated)

Changelog

Sourced from vite's changelog.

8.3.6 (2026-11-05)

Bug Fixes

  • await overlapping plugin container close calls (#23935) (175bbeb)
  • build: resolve dynamic imports with queries appended when collecting CSS dependencies (#23909) (df36558)
  • build: use stable module ids in chunk import map hash signatures (fix #23975) (#23976) (8069835)
  • bundled-dev: allow named imports from Node built-ins (#23858) (4260c75)
  • bundled-dev: reload when hmr cannot run an entry again (#23849) (a236886)
  • deps: update @rollup/plugin-alias to v6.0.1 (#23862) (67c965b)
  • deps: update all non-major dependencies (#23896) (46b91c5)
  • deps: update all non-major dependencies (#23966) (b3cb057)
  • deps: update rolldown-related dependencies (#23868) (a63eb87)
  • deps: update rolldown-related dependencies (#23967) (0105733)
  • dev: escape ANSI escape sequence for server.forwardConsole (#23933) (4f340fd)
  • html: remove adjacent module tags on the first line (#23823) (eab1dc2)
  • ignore pnpm's .modules.yaml as a Vite Task input (#23634) (95c2daf)
  • optimizer: detect cache dir precisely (#23912) (cc9bc21)
  • optimizer: resolve subpath imports (#) with Vite's resolver (#23959) (0fdd81e)
  • respect build.sourcemap from environment (#23879) (82e7aa0)
  • server: escape HTML attributes (#23995) (a270391)
  • server: preserve $ patterns in static alias replacements (#23703) (1b6ed05)
  • ssr: convert external require against built-in modules to import for ssr.target=webworker (#23759) (a711f1c)
  • use top-level input for SSR build when build.ssr: true (#23898) (90bc034)
  • wasm: reject .wasm outside server.fs (#23914) (64e2467)
  • watch files that have a query or hash referenced with new URL(..., import.meta.url) (#23780) (e954a9c)
  • worker: keep chunks conflicted with unused workers that are still used by a live worker (#23956) (7139ef3)

Performance Improvements

Miscellaneous Chores

Build System

  • generate sourcemaps in import-meta-current-dirname plugin (#23904) (20d355a)

8.3.5 (2026-10-21)

Bug Fixes

  • build: handle missing chunk import maps (#23777) (8d7623d)
  • build: include preload dependencies to chunk import map hashing (#23793) (4d16e7c)
  • bundled-dev: apply server.origin to asset URLs (#23683) (52ba877)
  • bundled-dev: declare utf-8 charset in fallback page (#23846) (197daf6)
  • bundled-dev: ignore build.chunkImportMap (#23685) (cfe917d)
  • bundled-dev: include user import.meta.env.* defines in the import.meta.env object (#23713) (6019aa7)
  • bundled-dev: map forwarded error stacks through the bundle source maps (#23741) (11fe1e4)

... (truncated)

Commits
  • 0fd9a29 release: v8.3.6 (#23996)
  • eab1dc2 fix(html): remove adjacent module tags on the first line (#23823)
  • a270391 fix(server): escape HTML attributes (#23995)
  • 7139ef3 fix(worker): keep chunks conflicted with unused workers that are still used b...
  • 0fdd81e fix(optimizer): resolve subpath imports (#) with Vite's resolver (#23959)
  • 8069835 fix(build): use stable module ids in chunk import map hash signatures (fix #2...
  • 95c2daf fix: ignore pnpm's .modules.yaml as a Vite Task input (#23634)
  • b3cb057 fix(deps): update all non-major dependencies (#23966)
  • 0105733 fix(deps): update rolldown-related dependencies (#23967)
  • 90bc034 fix: use top-level input for SSR build when build.ssr: true (#23898)
  • Additional commits viewable in compare view

Updates vite-plugin-solid from 2.11.14 to 2.11.15

Release notes

Sourced from vite-plugin-solid's releases.

vite-plugin-solid@2.11.15

Patch Changes

  • 62e2b75: Production builds now dedupe solid-js the same way dev does. A dependency with its own nested copy of solid-js no longer adds a second runtime to the bundle, which broke context lookups (#112).
  • a732eeb: Avoid overriding environments configured in Vitest workspaces and projects with the jsdom default
  • 9e67618: fix: exclude test mode from HMR setup
  • a7ec25f: Fix TypeError: Cannot read properties of undefined (reading 'extend') in tests on Vitest before 1.0 with @testing-library/jest-dom 6 or later installed (#141). The plugin now injects jest-dom's ESM vitest entry as an absolute path for those Vitest versions, because they load the CommonJS entry from a bare specifier.
  • 6cc30fe: Only inject the @testing-library/jest-dom Vitest setup file when the package resolves from the project root. Previously the check ran from the plugin's own location, so with pnpm a transitive jest-dom (for example via Storybook) made Vitest fail with Failed to load url .../@testing-library/jest-dom/vitest.
  • d0e47f1: Vitest runs keep the jsdom environment and the @testing-library/jest-dom setup file when test.server.deps.external already lists solid-js. The plugin used to drop its whole test config in that case.
  • f8439e8: The plugin no longer changes resolve.alias. An alias object in your config now keeps priority over aliases that later plugins add, such as vite-plugin-node-polyfills mapping path (#130).
  • df3ba8a: Compile modules whose id has the extension after the query, such as unplugin-icons' ~icons/mdi/folder?width=2em.tsx. Since 2.11.2 these were left to Vite's default JSX transform, which produced React code (#206). Custom extensions are now also matched when the query contains a dot.
  • b50c064: Keep $ServerOnly templates in client transforms while HMR is active so hot updates of components using $ServerOnly no longer throw template is not a function. An explicit solid.omitServerOnlyTemplates setting still takes precedence.
  • cd79ed9: Without ssr: true, modules loaded on the server now compile to non-hydratable SSR output instead of DOM output. Prerendering a client-rendered app with ssrLoadModule no longer throws "Client-only API called on the server side" (#64). Vitest keeps DOM output.
  • 9c17655: Server builds with ssr.target: 'webworker' now resolve the server build of solid-js. The plugin adds the worker export condition to that build, so renderToString and the other server APIs no longer resolve to their browser stubs (#153). This works on Vite 4 and later.
  • 8909380: Vite 8's dependency scan no longer breaks on .tsx files (issue #262). The plugin previously set optimizeDeps.rolldownOptions.transform.jsx: 'preserve' to stop Rolldown from injecting react/jsx-dev-runtime imports during the scan — but the scanner re-parses the transformed output as plain JS (import.meta.glob handling force-tags modules as js), so any .tsx with JSX was a hard PARSE_ERROR: Unexpected JSX expression that aborted the whole scan and skipped pre-bundling. The scan transform now uses the classic JSX runtime, which lowers JSX to bare React.createElement calls without injecting any import: the scan output is never executed, it only exists so rolldown can walk the import graph, so the undefined identifier is harmless. Backport of the fix already on the 3.0.0-next line.
  • 5d6846c: When the root config declares test.projects and leaves test.sharedViteServer unset, the plugin now sets it to false so every inline project resolves its own Vite config, as under Vitest 4. An explicit value is respected. Vitest 5 defaults the option to true, and a shared inline project takes its test options from the raw root block captured before any config hook runs, so it lost everything the plugin injects (the jsdom default, the @testing-library/jest-dom setup file, server.deps). Ports solidjs/solid-vite-plugin#370; refs #369.
  • 32adc90: In Vitest DOM tests (the jsdom default, no ssr option), the plugin now inlines solid-js and the packages that import it without a solid export condition, such as @solidjs/testing-library. Before, they stayed external, and the host runtime resolved their own imports. Node gets the browser condition from Vitest's worker --conditions, but Deno does not apply it in worker threads and resolves deno/node. Under Deno, @solidjs/testing-library loaded the server build of solid-js/web and rendersolidjs/solid-vite-plugin#369browser condition and loads one client-build instance. A test.server.deps.inline list is merged with the plugin's, and a test.server.deps.external entry for solid-js still opts out. With ssr: true, tests keep solid-js external as before.
  • 765a406: In jsdom and happy-dom tests, Node no longer gets the browser condition for packages that Vitest leaves external. Node-only packages such as msw/node now load under Vitest 4 and later (#125).
  • c750c34: Packages with a solid export condition that are declared only in the workspace root's package.json are now inlined for projects in that workspace. Before, Vitest loaded them with Node and failed with Unknown file extension ".jsx" (#157).
Changelog

Sourced from vite-plugin-solid's changelog.

2.11.15

Patch Changes

  • 62e2b75: Production builds now dedupe solid-js the same way dev does. A dependency with its own nested copy of solid-js no longer adds a second runtime to the bundle, which broke context lookups (#112).
  • a732eeb: Avoid overriding environments configured in Vitest workspaces and projects with the jsdom default
  • 9e67618: fix: exclude test mode from HMR setup
  • a7ec25f: Fix TypeError: Cannot read properties of undefined (reading 'extend') in tests on Vitest before 1.0 with @testing-library/jest-dom 6 or later installed (#141). The plugin now injects jest-dom's ESM vitest entry as an absolute path for those Vitest versions, because they load the CommonJS entry from a bare specifier.
  • 6cc30fe: Only inject the @testing-library/jest-dom Vitest setup file when the package resolves from the project root. Previously the check ran from the plugin's own location, so with pnpm a transitive jest-dom (for example via Storybook) made Vitest fail with Failed to load url .../@testing-library/jest-dom/vitest.
  • d0e47f1: Vitest runs keep the jsdom environment and the @testing-library/jest-dom setup file when test.server.deps.external already lists solid-js. The plugin used to drop its whole test config in that case.
  • f8439e8: The plugin no longer changes resolve.alias. An alias object in your config now keeps priority over aliases that later plugins add, such as vite-plugin-node-polyfills mapping path (#130).
  • df3ba8a: Compile modules whose id has the extension after the query, such as unplugin-icons' ~icons/mdi/folder?width=2em.tsx. Since 2.11.2 these were left to Vite's default JSX transform, which produced React code (#206). Custom extensions are now also matched when the query contains a dot.
  • b50c064: Keep $ServerOnly templates in client transforms while HMR is active so hot updates of components using $ServerOnly no longer throw template is not a function. An explicit solid.omitServerOnlyTemplates setting still takes precedence.
  • cd79ed9: Without ssr: true, modules loaded on the server now compile to non-hydratable SSR output instead of DOM output. Prerendering a client-rendered app with ssrLoadModule no longer throws "Client-only API called on the server side" (#64). Vitest keeps DOM output.
  • 9c17655: Server builds with ssr.target: 'webworker' now resolve the server build of solid-js. The plugin adds the worker export condition to that build, so renderToString and the other server APIs no longer resolve to their browser stubs (#153). This works on Vite 4 and later.
  • 8909380: Vite 8's dependency scan no longer breaks on .tsx files (issue #262). The plugin previously set optimizeDeps.rolldownOptions.transform.jsx: 'preserve' to stop Rolldown from injecting react/jsx-dev-runtime imports during the scan — but the scanner re-parses the transformed output as plain JS (import.meta.glob handling force-tags modules as js), so any .tsx with JSX was a hard PARSE_ERROR: Unexpected JSX expression that aborted the whole scan and skipped pre-bundling. The scan transform now uses the classic JSX runtime, which lowers JSX to bare React.createElement calls without injecting any import: the scan output is never executed, it only exists so rolldown can walk the import graph, so the undefined identifier is harmless. Backport of the fix already on the 3.0.0-next line.
  • 5d6846c: When the root config declares test.projects and leaves test.sharedViteServer unset, the plugin now sets it to false so every inline project resolves its own Vite config, as under Vitest 4. An explicit value is respected. Vitest 5 defaults the option to true, and a shared inline project takes its test options from the raw root block captured before any config hook runs, so it lost everything the plugin injects (the jsdom default, the @testing-library/jest-dom setup file, server.deps). Ports solidjs/solid-vite-plugin#370; refs #369.
  • 32adc90: In Vitest DOM tests (the jsdom default, no ssr option), the plugin now inlines solid-js and the packages that import it without a solid export condition, such as @solidjs/testing-library. Before, they stayed external, and the host runtime resolved their own imports. Node gets the browser condition from Vitest's worker --conditions, but Deno does not apply it in worker threads and resolves deno/node. Under Deno, @solidjs/testing-library loaded the server build of solid-js/web and rendersolidjs/solid-vite-plugin#369browser condition and loads one client-build instance. A test.server.deps.inline list is merged with the plugin's, and a test.server.deps.external entry for solid-js...

    Description has been truncated

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

| Package | From | To |
| --- | --- | --- |
| [@solidjs/router](https://github.com/solidjs/solid-router) | `1.0.0` | `1.0.1` |
| [solid-js](https://github.com/solidjs/solid) | `1.9.15` | `1.9.18` |
| [@axe-core/playwright](https://github.com/dequelabs/axe-core-npm) | `4.13.0` | `4.14.0` |
| [@biomejs/biome](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome) | `2.5.15` | `2.6.6` |
| [@playwright/test](https://github.com/microsoft/playwright) | `1.63.0` | `1.65.0` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `8.3.2` | `8.3.6` |
| [vite-plugin-solid](https://github.com/solidjs/solid-vite-plugin) | `2.11.14` | `2.11.15` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `5.0.3` | `5.1.0` |



Updates `@solidjs/router` from 1.0.0 to 1.0.1
- [Release notes](https://github.com/solidjs/solid-router/releases)
- [Changelog](https://github.com/solidjs/solid-router/blob/main/CHANGELOG.md)
- [Commits](https://github.com/solidjs/solid-router/commits/v1.0.1)

Updates `solid-js` from 1.9.15 to 1.9.18
- [Release notes](https://github.com/solidjs/solid/releases)
- [Changelog](https://github.com/solidjs/solid/blob/main/CHANGELOG.md)
- [Commits](https://github.com/solidjs/solid/commits)

Updates `@axe-core/playwright` from 4.13.0 to 4.14.0
- [Release notes](https://github.com/dequelabs/axe-core-npm/releases)
- [Changelog](https://github.com/dequelabs/axe-core-npm/blob/develop/CHANGELOG.md)
- [Commits](dequelabs/axe-core-npm@v4.13.0...v4.14.0)

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

Updates `@playwright/test` from 1.63.0 to 1.65.0
- [Release notes](https://github.com/microsoft/playwright/releases)
- [Commits](microsoft/playwright@v1.63.0...v1.65.0)

Updates `vite` from 8.3.2 to 8.3.6
- [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/v8.3.6/packages/vite)

Updates `vite-plugin-solid` from 2.11.14 to 2.11.15
- [Release notes](https://github.com/solidjs/solid-vite-plugin/releases)
- [Changelog](https://github.com/solidjs/solid-vite-plugin/blob/main/CHANGELOG.md)
- [Commits](https://github.com/solidjs/solid-vite-plugin/compare/vite-plugin-solid@2.11.14...vite-plugin-solid@2.11.15)

Updates `vitest` from 5.0.3 to 5.1.0
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.1.0/packages/vitest)

---
updated-dependencies:
- dependency-name: "@solidjs/router"
  dependency-version: 1.0.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: solid-js
  dependency-version: 1.9.18
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: "@axe-core/playwright"
  dependency-version: 4.14.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: "@biomejs/biome"
  dependency-version: 2.6.6
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: "@playwright/test"
  dependency-version: 1.65.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
- dependency-name: vite
  dependency-version: 8.3.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: vite-plugin-solid
  dependency-version: 2.11.15
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-minor-patch
- dependency-name: vitest
  dependency-version: 5.1.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants