Bump the all-npm-dependencies group across 1 directory with 6 updates

[dependabot]

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

Package	From	To
vue	3.5.18	3.5.22
@biomejs/biome	2.1.3	2.2.5
@wxt-dev/module-vue	1.0.2	1.0.3
typescript	5.9.2	5.9.3
vue-tsc	3.0.5	3.1.0
wxt	0.20.7	0.20.11

Updates vue from 3.5.18 to 3.5.22

Release notes

Sourced from vue's releases.

v3.5.22

For stable releases, please refer to CHANGELOG.md for details. For pre-releases, please refer to CHANGELOG.md of the minor branch.

v3.5.21

For stable releases, please refer to CHANGELOG.md for details. For pre-releases, please refer to CHANGELOG.md of the minor branch.

v3.5.20

For stable releases, please refer to CHANGELOG.md for details. For pre-releases, please refer to CHANGELOG.md of the minor branch.

v3.5.19

For stable releases, please refer to CHANGELOG.md for details. For pre-releases, please refer to CHANGELOG.md of the minor branch.

Changelog

Sourced from vue's changelog.

3.5.22 (2025-09-25)

Bug Fixes

• compiler-core: identifiers in switch-case should not be inferred as references (#13923) (5953c9f)
• compiler-dom: nodes with v-once shouldn't be stringified (#13878) (95c1975)
• compiler-sfc: add support for @vue-ignore in runtime type resolution (#13906) (ba7f7f9)
• compiler-sfc: enhance inferRuntimeType to support TSMappedType with indexed access (#13848) (e388f1a), closes #13847
• compiler-sfc: ensure css custom properties do not start with a digit (#13870) (9c27951)
• compiler-sfc: ensure props bindings register before compiling template (#13922) (abd5638), closes #13920
• compiler-ssr: ensure v-show has a higher priority in SSR (#12171) (836b829), closes #12162
• custom-element: properly mount multiple Teleports in custom element component w/ shadowRoot false (#13900) (5e1e791), closes #13899
• custom-element: set prop runs pending mutations before disconnect (#13897) (c4a88cd), closes #13315
• custom-element: use PatchFlags.BAIL for slot when props are present (#13907) (5358bca), closes #13904
• reactivity: respect readonly during ref unwrapping (#13905) (aba7fed), closes #13903
• reactivity: update iterator to check for completion instead of value presence (#13761) (2078f8b)
• runtime-core: simplify block-tracking disabling in h helper (#13841) (75220c7)
• transition-group: run forceReflow on the correct document (fix #13849) (#13853) (1be5ddf)
• types: more precise types for Events and added missing definitions (#9675) (8bb8fb2)
• types: set dom stub type to never instead of {} (#13915) (8620a61), closes #11564
• types: widen directive arg type from string to any (#13758) (4b71706), closes #13757

Features

• custom-element: allow specifying additional options for shadowRoot in custom elements (#12965) (47e628d), closes #12964

Reverts

• Revert "fix(hmr): prevent VUE_HMR_RUNTIME from being overwritten by vue runtime in 3rd-party libraries" (#13925) (6b68f72), closes #13925

3.5.21 (2025-09-02)

Bug Fixes

• compiler-core: force dynamic slots when slot referencing scope vars (#9427) (99d54b2), closes #9380
• compiler-sfc: check lang before attempt to compile script (#13508) (55922ff), closes #8368
• compiler-sfc: support ${configDir} in paths for TypeScript 5.5+ (#13491) (8696e34), closes #13484
• compiler-sfc: support global augments with named exports (#13789) (35da3c6)
• custom-element: prevent defineCustomElement from mutating the options object (#13791) (e322436)
• hmr: prevent __VUE_HMR_RUNTIME__ from being overwritten by vue runtime in 3rd-party libraries (#13817) (1392734), closes vitejs/vite-plugin-vue#644
• hmr: prevent update unmounting component during HMR reload (#13815) (ef20b86), closes vitejs/vite-plugin-vue#599
• runtime-core: disable tracking block in h function (#8213) (8f6b505), closes #6913
• runtime-core: use separate emits caches for components and mixins (#11661) (15fc75f)
• Suspence: handle Suspense + KeepAlive HMR updating edge case (#13076) (5d75a17), closes #13075

... (truncated)

Commits

• 5a8aa0b release: v3.5.22
• 1be5ddf fix(transition-group): run forceReflow on the correct document (fix #13849)...
• d44a5a9 chore(deps): update build (#13856)
• c8a9917 chore(deps): update dependency jsdom to v27 (#13913)
• b46481a chore(deps): update compiler (#13857)
• 8593647 chore(deps): update test (#13882)
• f2487d8 chore(deps): update actions/github-script action to v8 (#13885)
• b374ec7 chore(deps): update actions/setup-node action to v5 (#13912)
• 9612b95 chore(deps): update all non-major dependencies (#13883)
• 5953c9f fix(compiler-core): identifiers in switch-case should not be inferred as refe...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vue since your current version.

Updates @biomejs/biome from 2.1.3 to 2.2.5

Release notes

Sourced from @​biomejs/biome's releases.

Biome CLI v2.2.5

2.2.5

Patch Changes

• #7597 5c3d542 Thanks @​arendjr! - Fixed #6432: useImportExtensions now works correctly with aliased paths.

• #7269 f18dac1 Thanks @​CDGardner! - Fixed #6648, where Biome's noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

  Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

  On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.

  // Ended up as: - const t = "Text"
  const t = <>Text</>
  // Ended up as: - const e = t ? "Option A" : "Option B"
  const e = t ? <>Option A</> : <>Option B</>
  /* Ended up as:
  function someFunc() {
  return "Content desired to be a multi-line block of text."
  }
  */
  function someFunc() {
  return <>
  Content desired to be a multi-line
  block of text.
  <>
  }

  The proposed update was to align Biome's reaction to this rule with ESLint's; the aforementioned examples will now be supported from Biome's perspective, thus valid use of fragments.

  // These instances are now valid and won't be called out by noUselessFragments.
  const t = <>Text</>
  const e = t ? <>Option A</> : <>Option B</>
  function someFunc() {
  return <>
  Content desired to be a multi-line
  block of text.
  <>
  }

... (truncated)

Changelog

Sourced from @​biomejs/biome's changelog.

2.2.5

Patch Changes

• #7597 5c3d542 Thanks @​arendjr! - Fixed #6432: useImportExtensions now works correctly with aliased paths.

• #7269 f18dac1 Thanks @​CDGardner! - Fixed #6648, where Biome's noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

  Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

  On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.

  // Ended up as: - const t = "Text"
  const t = <>Text</>
  // Ended up as: - const e = t ? "Option A" : "Option B"
  const e = t ? <>Option A</> : <>Option B</>
  /* Ended up as:
  function someFunc() {
  return "Content desired to be a multi-line block of text."
  }
  */
  function someFunc() {
  return <>
  Content desired to be a multi-line
  block of text.
  <>
  }

  The proposed update was to align Biome's reaction to this rule with ESLint's; the aforementioned examples will now be supported from Biome's perspective, thus valid use of fragments.

  // These instances are now valid and won't be called out by noUselessFragments.
  const t = <>Text</>
  const e = t ? <>Option A</> : <>Option B</>
  function someFunc() {
  return <>
  Content desired to be a multi-line
  block of text.
  <>
  }

• #7498 002cded Thanks @​siketyan! - Fixed #6893: The useExhaustiveDependencies rule now correctly adds a dependency that is captured in a shorthand object member. For example:

... (truncated)

Commits

• 521d149 ci: release (#7478)
• cadad2c feat(lint): implement noVueDuplicateKeys rule (#7542)
• 9637f93 feat: add useConsistentArrowReturn options (#7457)
• 1b61631 feat(lint): add noReactForwardRef rule (#7509)
• 74d3c56 chore: add convex to bronze sponsors (#7566)
• 3f06e19 feat(linter): implement noDeprecatedImports (#7520)
• a0039fd feat(linter): implement noUnusedExpressions (#7511)
• fd126d7 chore: fix markdown syntax in changelog
• b2da976 chore: fix changelog formatting
• 0109940 chore: repair changelog (#7477)
• Additional commits viewable in compare view

Updates @wxt-dev/module-vue from 1.0.2 to 1.0.3

Release notes

Sourced from @​wxt-dev/module-vue's releases.

@​wxt-dev/module-vue v1.0.3

compare changes

🏡 Chore

• Add funding links to package.json files (#1446)
• Use PNPM 10's new catelog feature (#1493)
• Move production dependencies to PNPM 10 catelog (#1494)
• Stop using PNPM catalog (#1644)
• Upgrade @aklinker1/check to v2 (#1647)
• Wxt & @​wxt-dev/module-vue support Vite 7 (#1771)
• deps: Upgrade typescript from 5.8.3 to 5.9.2 (a6eef643)
• Create script for managing dependency upgrades (#1875)
• deps: Upgrade all dev dependencies (#1876)

❤️ Contributors

• Aaron (@​aklinker1)
• Ayu (@​ayu-exorcist)
• Okinea Dev hi@okinea.dev

Changelog

Sourced from @​wxt-dev/module-vue's changelog.

v1.0.3

compare changes

🏡 Chore

• Add funding links to package.json files (#1446)
• Use PNPM 10's new catelog feature (#1493)
• Move production dependencies to PNPM 10 catelog (#1494)
• Stop using PNPM catalog (#1644)
• Upgrade @aklinker1/check to v2 (#1647)
• Wxt & @​wxt-dev/module-vue support Vite 7 (#1771)
• deps: Upgrade typescript from 5.8.3 to 5.9.2 (a6eef643)
• Create script for managing dependency upgrades (#1875)
• deps: Upgrade all dev dependencies (#1876)

❤️ Contributors

• Aaron (@​aklinker1)
• Ayu (@​ayu-exorcist)
• Okinea Dev hi@okinea.dev

Commits

• 55fed67 chore(release): @​wxt-dev/module-vue v1.0.3
• 7a81472 chore(deps): Upgrade all dev dependencies (#1876)
• 9399d8d chore: Create script for managing dependency upgrades (#1875)
• a6eef64 chore(deps): Upgrade typescript from 5.8.3 to 5.9.2
• e7db119 chore: wxt & @​wxt-dev/module-vue support Vite 7 (#1771)
• 6f970ef chore: Upgrade @aklinker1/check to v2 (#1647)
• 4add882 chore: Stop using PNPM catalog (#1644)
• 28cff9c chore: Move production dependencies to PNPM 10 catelog (#1494)
• 8ce197b chore: Use PNPM 10's new catelog feature (#1493)
• e20de4c chore: Add funding links to package.json files (#1446)
• Additional commits viewable in compare view

Updates typescript from 5.9.2 to 5.9.3

Release notes

Sourced from typescript's releases.

TypeScript 5.9.3

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

• fixed issues query for Typescript 5.9.0 (Beta).
• fixed issues query for Typescript 5.9.1 (RC).
• No specific changes for TypeScript 5.9.2 (Stable)
• fixed issues query for Typescript 5.9.3 (Stable).

Downloads are available on:

• npm

Commits

• c63de15 Bump version to 5.9.3 and LKG
• 8428ca4 🤖 Pick PR #62438 (Fix incorrectly ignored dts file fr...) into release-5.9 (#...
• a131cac 🤖 Pick PR #62351 (Add missing Float16Array constructo...) into release-5.9 (#...
• 0424333 🤖 Pick PR #62423 (Revert PR 61928) into release-5.9 (#62425)
• bdb641a 🤖 Pick PR #62311 (Fix parenthesizer rules for manuall...) into release-5.9 (#...
• 0d9b9b9 🤖 Pick PR #61978 (Restructure CI to prepare for requi...) into release-5.9 (#...
• 2dce0c5 Intentionally regress one buggy declaration output to an older version (#62163)
• See full diff in compare view

Updates vue-tsc from 3.0.5 to 3.1.0

Release notes

Sourced from vue-tsc's releases.

v3.1.0

[!IMPORTANT]
Vue 2 and vue-class-component support has been removed, please refer to Discussion #5455 for detail.

Performance

• perf(language-core): drop internal component (#5532) - Thanks to @​KazariEX!

Other Changes

• refactor: drop Vue 2 support (#5636) - Thanks to @​KazariEX!
• chore(lint): enforce use of type-only imports (#5658) - Thanks to @​so1ve!
• ci: upgrade node version (#5668) - Thanks to @​so1ve!
• refactor(typescript-plugin): move reactivity analysis logic to a seperate typescript plugin (#5672) - Thanks to @​KazariEX!

Also, thanks to the motivating launch of Vue ECharts v8!

❤️ Thanks to Our Sponsors

... (truncated)

Changelog

Sourced from vue-tsc's changelog.

3.1.0 (2025-09-28)

Performance

• perf(language-core): drop internal component (#5532) - Thanks to @​KazariEX!

Other Changes

• refactor: drop Vue 2 support (#5636) - Thanks to @​KazariEX!
• chore(lint): enforce use of type-only imports (#5658) - Thanks to @​so1ve!
• ci: upgrade node version (#5668) - Thanks to @​so1ve!
• refactor(typescript-plugin): move reactivity analysis logic to a seperate typescript plugin (#5672) - Thanks to @​KazariEX!

3.0.8 (2025-09-23)

Features

• feat(vscode): introduce vue.server.path setting (#5647)

Bug Fixes

• fix(language-core): initialize properties of VueVirtualCode in constructor (#5635) - Thanks to @​KazariEX!
• fix(vscode): flatten reactivity visualization decorators (#5642) - Thanks to @​KazariEX!
• fix(vscode): normalize reactivity visualization ranges
• fix(vscode): patch typescriptServerPlugin languages without FS hack
• fix(language-service): do not provide semantic tokens and document highlights for non-file scheme files (#5653) - Thanks to @​KazariEX!

Performance

• perf(typescript-plugin): redo single-file language service for reactivity visualization (#5652)

Other Changes

• refactor(typescript-plugin): externalize reactivity analysis logic (#5645) - Thanks to @​KazariEX!

3.0.7 (2025-09-12)

Bug Fixes

• fix(vscode): show welcome page only when opening a Vue file
• fix(language-core): generate slot parameters in the same way as interpolation (#5618) - Thanks to @​KazariEX!
• fix(language-core): do not generate variables for builtin directives - Thanks to @​KazariEX!

Other Changes

• docs(vscode): add descriptions for premium feature configurations (#5612) - Thanks to @​KazariEX!
• refactor(typescript-plugin): explicitly request parameters (#5623)
• chore(lint): enable @typescript-eslint/no-unnecessary-condition (#5630)
• refactor(language-server): reimplement Reactivity Visualization in typescript plugin (#5632)
• refactor(language-server): parsing interpolations in extension client (#5633)

... (truncated)

Commits

• 1308528 v3.1.0 (#5657)
• 39eb65c perf(language-core): drop internal component (#5532)
• 10d056b v3.0.8 (#5654)
• 75dca51 v3.0.7 (#5621)
• bec4f08 v3.0.6 (#5608)
• 0ed384f chore: update volar to 2.4.23
• 882abc0 refactor(language-core): generate setup returns on demand
• 112f65b refactor(language-core): wrap __VLS_InheritedAttrs with Partial at defini...
• See full diff in compare view

Updates wxt from 0.20.7 to 0.20.11

Release notes

Sourced from wxt's releases.

wxt v0.20.11

compare changes

🩹 Fixes

• Split wxt/testing into separate modules to fix issues with jsdom and happy-dom (#1844)
• input_components is supported by mv3 (#1881)

🏡 Chore

• deps: Upgrade project subdependencies (#1882)

❤️ Contributors

• Aaron (@​aklinker1)
• Qijia Liu liumeo@pku.edu.cn
• Marcellino Ornelas (@​marcellino-ornelas)

wxt v0.20.10

compare changes

🏡 Chore

• deps: Upgrade non-breaking production dependencies (#1877)
• deps: Upgrade web-ext-run to support CDP (#1879)
• deps: publish-browser-extension upgrade (#1880)

❤️ Contributors

• Aaron (@​aklinker1)

wxt v0.20.9

compare changes

🩹 Fixes

• types: Use TType for DocumentEventMap key in ctx.addEventListener (#1863)
• Prevent Unlisted CSS from being excluded in the build when using CSS preprocessor (#1590)

🏡 Chore

• deps: Upgrade oxlint from 0.16.8 to 1.14.0 (a01928e0)
• deps: Upgrade typescript from 5.8.3 to 5.9.2 (a6eef643)
• Upgrade nano-spawn to v1 (5fefd8e0)
• Upgrade faker to v10 (984568e0)
• Upgrade dotenv to v17.2.2 (380a9630)
• Upgrade happy-dom to v18.0.1 (c1c3d3b7)
• Create script for managing dependency upgrades (#1875)
• deps: Upgrade all dev dependencies (#1876)

... (truncated)

Commits

• 84405a3 chore(release): wxt v0.20.11
• bdf795c chore(deps): Upgrade project subdependencies (#1882)
• ab73084 fix: input_components is supported by mv3 (#1881)
• e9fb4c5 fix: Split wxt/testing into separate modules to fix issues with jsdom and...
• bc54f52 chore(release): @​wxt-dev/module-react v1.1.5
• 9170159 chore(deps): Support @​vitejs/plugin-react@​5
• fa657a0 chore(release): wxt v0.20.10
• 24920dd chore(deps): publish-browser-extension upgrade (#1880)
• eb0b372 chore(deps): Upgrade web-ext-run to support CDP (#1879)
• 8f5f4f6 chore(deps): Upgrade non-breaking production dependencies (#1877)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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

[dependabot]

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