[dependabot]

Bumps the npm-development group in /ui with 4 updates: @types/node, eslint, globals and vite-plugin-solid.

Updates @types/node from 26.6.5 to 26.6.6

Commits

• See full diff in compare view

Updates eslint from 10.13.0 to 10.14.0

Release notes

Sourced from eslint's releases.

v10.14.0

Features

• d23a7f9 feat: fix property descriptor handling in func-name-matching (#21400) (xbinaryx)

Bug Fixes

• 4a12580 fix: require minimatch 10.2.6 to avoid vulnerable brace-expansion (#21460) (lumir)
• 827a8f3 fix: no-restricted-globals crash on global objects as property values (#21449) (xbinaryx)
• 161558a fix: handle LS, PS and empty hashbang comments (#21419) (lumir)
• 6194939 fix: no-invalid-this crash on accessor fields without initializer (#21442) (xbinaryx)
• 9155e14 fix: Update @​humanfs/node dependency version (#21434) (Nicholas C. Zakas)
• cb2b9d4 fix: avoid invalid object-shorthand fixes for super methods (#21323) (dvd233)
• 5ee3915 fix: yoda invalid autofix at statement start (#21424) (Daniel Pinto)

Documentation

• 0f94f47 docs: remove zh-hans from docs language switcher (#21437) (lumir)
• dab466e docs: Update README (GitHub Actions Bot)
• 97431f8 docs: replace --rulesdir with a virtual plugin in custom rules docs (#21452) (Pixel)
• 7697550 docs: Update README (GitHub Actions Bot)
• 0c699d5 docs: Remove Tidelift commercial support (#21416) (Milos Djermanovic)
• 0880666 docs: update loadESLint() documentation for v10 (#21374) (Minseon Kim)
• e06fe87 docs: Revise AI acknowledgment options in PR template (#21414) (Nicholas C. Zakas)

Chores

• 0e2ab70 ci: disable eslint-plugin-unicorn ecosystem test (#21462) (Francesco Trotta)
• 6e3f988 chore: update github/codeql-action action to v4.39.1 (#21450) (renovate[bot])
• a031c40 chore: update ecosystem plugins (#21445) (ESLint Bot)
• 67d2ca2 chore: add troubleshooting page URL to circular fixes warning message (#21429) (Milos Djermanovic)
• 276021d chore: update github/codeql-action action to v4.39.0 (#21432) (renovate[bot])
• 449724e chore: update ecosystem plugins (#21420) (ESLint Bot)
• 8ffeb8c chore: update dependency prettier to v3.9.10 (#21417) (renovate[bot])

Commits

• 12cbff4 10.14.0
• 6b696e7 Build: changelog update for 10.14.0
• 0e2ab70 ci: disable eslint-plugin-unicorn ecosystem test (#21462)
• 4a12580 fix: require minimatch 10.2.6 to avoid vulnerable brace-expansion (#21460)
• 0f94f47 docs: remove zh-hans from docs language switcher (#21437)
• dab466e docs: Update README
• 827a8f3 fix: no-restricted-globals crash on global objects as property values (#21449)
• 97431f8 docs: replace --rulesdir with a virtual plugin in custom rules docs (#21452)
• 6e3f988 chore: update github/codeql-action action to v4.39.1 (#21450)
• 161558a fix: handle LS, PS and empty hashbang comments (#21419)
• Additional commits viewable in compare view

Updates globals from 17.13.0 to 17.14.0

Release notes

Sourced from globals's releases.

v17.14.0

• Update globals (2026-11-01) (#355) 7abfb5d

---

sindresorhus/globals@v17.13.0...v17.14.0

Commits

• 3080111 17.14.0
• c61cc23 Tweaks
• 7abfb5d Update globals (2026-11-01) (#355)
• See full diff 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 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).

Commits

• 884edff chore: point package metadata at the renamed solid-vite-plugin repo (#502)
• 7c9885d Merge pull request #429 from solidjs/changeset-release/main
• 591c9e4 Version Packages
• 98bf9f7 Merge pull request #491 from solidjs/claude/solid-1x-release-ithwfa
• 7afa18a test: link jest-dom into the fake projects in jest-dom.test.ts
• 4bf407b Merge PR #238
• 9ad07fc Merge PR #452
• 4cdffff Merge PR #426
• e01ce9a Merge PR #412
• dae0ea1 Merge PR #445
• 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

[github-actions]

Coverage Report for ui

Status	Category	Percentage	Covered / Total
🔵	Lines	97.27% ⬇️ -0.03 pp	9972 / 10251
🔵	Statements	95.58% ⬇️ -0.03 pp	13981 / 14627
🔵	Functions	95.45% 🟰 ±0 pp	3986 / 4176
🔵	Branches	85.54% ⬆️ +0.52 pp	5257 / 6145

File Coverage

No changed files found.

Generated in workflow #277 for commit 61e0661 by the Vitest Coverage Report Action