fix(deps): update dependency vue-router to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vue-router (source)	^4.5.0 → ^5.0.0

---

Release Notes

vuejs/router (vue-router)

v5.0.3

Compare Source

   🚨 Breaking Changes

• experimental:
  • Make miss() throw internally and return never  -  by @​posva (077e1)
  • Add reroute() and deprecate NavigationResult  -  by @​posva (308db)
  • Remove selectNavigationResult  -  by @​posva (9e88a)

   🚀 Features

• Support _parent in nested folders  -  by @​posva (0a37f)
• Warn on _parent conflict  -  by @​posva (182fe)
• Set _parent as non matchable by default  -  by @​posva (8f91c)
• Warn on conflicting components for routes  -  by @​posva (34ace)
• Use type module  -  by @​posva (dc9ff)
• Add deprecation warning for next() callback in navigation guards  -  by @​posva (797f5)
• Extract alias from definePage  -  by @​posva (835df)
• Display aliases in logs  -  by @​posva (7aa60)
• Deprecate new NavigationResult(to) in favor of reroute(to)  -  by @​posva (382e3)
• experimental:
  • Handle aliasOf in resolvers  -  by @​posva (8fe45)
  • Generate aliases from override in resolver  -  by @​posva (a00ac)
  • Warn against non absolute aliases  -  by @​posva (476c6)

   🐞 Bug Fixes

• Avoid non matchable routes in auto-routes  -  by @​posva (48649)
• Handle quotes in d.ts  -  by @​posva (d7764)
• Avoid route entry in map for _parent  -  by @​posva (1dfcc)
• Handle nested groups  -  by @​posva (4a4be)
• Stable route ordering for group folders with same path  -  by @​posva (1db94)
• Correct route ordering for group nodes with inflated scores  -  by @​posva (515f4)
• Cleanup old route overrides  -  by @​posva (b28a7)
• Remove name from _parent.vue files  -  by @​posva (6e8f1)
• ci:
  • Format sponsor files before change detection  -  by @​posva (f68d6)
  • Use manual git commit in update-sponsors  -  by @​posva (8ee99)
• experimental:
  • Resolve TS errors in resolver/router type hierarchy  -  by @​posva (a86f1)
• types:
  • Relax RouteMapGeneric constraint for interface-based RouteNamedMap  -  by @​YevheniiKotyrlo in #​2624 (cdf7b)
• volar:
  • Use ts.getTokenPosOfNode instead of node.getStart  -  by @​KazariEX in #​2630 (0b050)

   🏎 Performance

• Avoid merging empty object in record  -  by @​posva (4213e)

    View changes on GitHub

v5.0.2

Compare Source

   🐞 Bug Fixes

• Remove devtools from iife build  -  by @​posva (58c03)
• Loose version check vue-router  -  by @​posva (90e4b)
• volar: Empty options  -  by @​posva (02275)

    View changes on GitHub

v5.0.1

Compare Source

   🐞 Bug Fixes

• volar: Make typed plugin work with vue-tsc  -  by @​peter50216 in #​2607 (7845e)

    View changes on GitHub

v5.0.0

Compare Source

Vue Router 5 is a boring release, it merges unplugin-vue-router into the core package with no breaking changes. The only exception is that the iife build no longer includes @vue/devtools-api because it has been upgraded to v8 and does not expose an IIFE build itself. You can track that change in this issue. See the migration guide for instructions on how to upgrade from unplugin-vue-router to Vue Router 5.

   🚀 Features

• experimental: Query params are optional by default  -  by @​posva (78913)
• Add volar plugins  -  by @​posva (530ac)
• Add data loaders as experimental  -  by @​posva (ab895)
• Add route json schema  -  by @​posva (20675)
• Upgrade devtools-api to v7  -  by @​posva (17b84)
• Upgrade devtools to v8  -  by @​posva (b8aa2)
• Runtime error on missing param parsers  -  by @​posva (3444b)
• volar: Allow rootDir option  -  by @​posva (df65a)

   🐞 Bug Fixes

• Avoid breaking older browsers support  -  by @​posva (c7ba4)
• Trigger navigation guards when keep-alive component is reactivated for different route  -  by @​babu-ch and @​posva in #​2604 (c7735)
• Add automatic types for param parsers  -  by @​posva (0fb5d)
• Param parsers when dts is not at root  -  by @​posva (16b39)
• Expose resolveOptions for unplugin  -  by @​posva (35543)
• Escape tildes in paths  -  by @​posva (aac2e)
• volar: Upgrade config read  -  by @​posva (e3024)

    View changes on GitHub

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @auth0/auth0-vue@2.5.0
npm error Found: vue-router@5.0.3
npm error node_modules/vue-router
npm error   vue-router@"^5.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional vue-router@"^4.0.12" from @auth0/auth0-vue@2.5.0
npm error node_modules/@auth0/auth0-vue
npm error   @auth0/auth0-vue@"^2.5.0" from the root project
npm error
npm error Conflicting peer dependency: vue-router@4.6.4
npm error node_modules/vue-router
npm error   peerOptional vue-router@"^4.0.12" from @auth0/auth0-vue@2.5.0
npm error   node_modules/@auth0/auth0-vue
npm error     @auth0/auth0-vue@"^2.5.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-09T09_44_51_637Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-09T09_44_51_637Z-debug-0.log

[matthieugouel]

@claude can you fix this renovate dependency update change error? The CI is failing.

[matthieugouel]

Claude finished @matthieugouel's task in 3m 28s —— View job

---

Fixing Dependency Conflict

• Analyze the dependency conflict
• Apply fix (.npmrc with legacy-peer-deps=true)
• Commit and push changes

Root Cause: @auth0/auth0-vue@2.5.0 declares vue-router@"^4.0.12" as an optional peer dependency, but npm v7+ enforces peer dependency version ranges strictly. Since vue-router v5 is outside the ^4.0.12 range, npm refused to regenerate the lockfile — leaving package.json (v5) and package-lock.json (v4) out of sync, which caused npm ci in Docker to fail.

Fix applied: Added .npmrc with legacy-peer-deps=true. This is safe because:

• vue-router is only an optional peer dependency of @auth0/auth0-vue
• vue-router v5 is API-compatible with v4 (per the v5.0.0 release notes)

One more step needed: The package-lock.json still needs to be regenerated with vue-router v5. To trigger this, check the "rebase/retry" checkbox in the PR description above — Renovate will re-run and regenerate the lockfile using the new .npmrc setting, which will unblock the CI.
|

[matthieugouel]

@claude the rebase of renovate remove your commit, could you add it back? I'll regenerate the package-lock.json myself

[matthieugouel]

Claude finished @matthieugouel's task in 36s —— View job

---

Adding back .npmrc fix

• Analyze the request
• Create .npmrc with legacy-peer-deps=true
• Commit and push

Done! The .npmrc file has been added back. You can now regenerate package-lock.json locally with:

npm install

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.