Skip to content

Update dependency vue-router to v5 - #572

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vue-router-5.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vue-router-5.x

Conversation

@renovate

@renovate renovate Bot commented Feb 1, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
vue-router (source) 3.6.5 → 5.4.0 age confidence

Release Notes

vuejs/router (vue-router)

v5.4.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v5.3.1

Compare Source

   🐞 Bug Fixes
  • experimental: Handle non-string params for isActive  -  by @​posva (92cfd)
    View changes on GitHub

v5.3.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v5.2.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v5.1.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v5.0.7

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v5.0.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
  • Track definePage imports per-file to fix named view race condition  -  by @​posva (11191)
  • Avoid double decoding hash on string location  -  by @​posva (1578c)
    View changes on GitHub

v5.0.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.3

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v5.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.1

Compare Source

   🐞 Bug Fixes
    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
   🐞 Bug Fixes
    View changes on GitHub

v4.6.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.6.3

Compare Source

Please refer to CHANGELOG.md for details.

v4.6.2

Compare Source

Please refer to CHANGELOG.md for details.

v4.6.1

Compare Source

Please refer to CHANGELOG.md for details.

v4.6.0

Compare Source

Please refer to CHANGELOG.md for details.

v4.5.1

Compare Source

Please refer to CHANGELOG.md for details.

v4.5.0

Compare Source

Please refer to CHANGELOG.md for details.

v4.4.5

Compare Source

Please refer to CHANGELOG.md for details.

v4.4.4

Compare Source

Please refer to CHANGELOG.md for details.

v4.4.3

Compare Source

Please refer to CHANGELOG.md for details.

v4.4.2

Compare Source

Please refer to CHANGELOG.md for details.

v4.4.1

Compare Source

Please refer to CHANGELOG.md for details.

v4.4.0

Compare Source

Please refer to CHANGELOG.md for details.

v4.3.3

Compare Source

Please refer to CHANGELOG.md for details.

v4.3.2

Compare Source

Please refer to CHANGELOG.md for details.

v4.3.1

Compare Source

Please refer to CHANGELOG.md for details.

v4.3.0

Compare Source

Please refer to CHANGELOG.md for details.

v4.2.5

Compare Source

Please refer to CHANGELOG.md for details.

v4.2.4

Compare Source

Please refer to CHANGELOG.md for details.

v4.2.3

Compare Source

Please refer to CHANGELOG.md for details.

v4.2.2

Compare Source

Please refer to CHANGELOG.md for details.

v4.2.1

Compare Source

Please refer to CHANGELOG.md for details.

v4.2.0

Compare Source

Please refer to CHANGELOG.md for details.

v4.1.6

Compare Source

Please refer to CHANGELOG.md for details.

v4.1.5

Compare Source

Please refer to CHANGELOG.md for details.

v4.1.4

Compare Source

Please refer to CHANGELOG.md for details.

v4.1.3

Compare Source

Please refer to CHANGELOG.md for details.

v4.1.2

Compare Source

Please refer to CHANGELOG.md for details.

v4.1.1

Compare Source

Please refer to CHANGELOG.md for details.

v4.1.0

Compare Source

Vue Router 4.1

We are excited to announce the release of Vue Router 4.1 with a few new interesting features, better support for Node ESM and no breaking changes.

Omitting the component/components option in routes

It's now possible to completely omit the component option when defining routes with children. While nested routes are about defining layouts, they are also directly connected to a path and users often found themselves defining a pass through component that would just render a <RouterView> component to reuse the path structure. You can now simplify this to:

- import { RouterView } from 'vue-router'
- import { h } from 'vue'
-
 const routes = [
   {
     path: '/admin',
-     component: () => h(RouterView),
     children: [
       { path: 'users', component: AdminUserList },
       { path: 'users/:id', component: AdminUserDetails },
     ],
   },
 ]

In other words, you can now nest paths without having to define a component.

Passing History State in navigations

Passing History State through router.push() has been implemented and used by the router since its version 4.0 but hasn't been exposed as a public API until now. This enables passing a state property when calling router.push() or router.replace(). This is useful to pass global state to be associated with the history entry that cannot be shared by copying the URL. One common example of this are Modals:

// go to /users/24 but show a modal instead
router.push({ name: 'UserDetail', params: { id: 24 } state: { backgroundView: ... } })

To see a full example, check the modal e2e test, it has been updated to use the state property.

It's worth noting this shouldn't be used to pass fetched data or complex objects such as classes because of type and size limitations. Check the History State documentation for more information about the state property.

Given the nature of the <RouterView>'s route prop, there is also a new function loadRouteLocation() that can be used on a resolved route location to load a route with lazy loading:

import { loadRouteLocation } from 'vue-router'

const loadedRoute = await loadRouteLocation(router.resolve('/users/24'))
Typed Routes

RouterLink to autocomplete

In v4.1 we were initially planning to introduce types to automatically detect the params from a path property, creating autocomplete and type safety in router.push() and <RouterLink>'s to prop. It was implemented but also turned out to be extremely slow after ~50 routes due to the nature of the types relying on nesting and complex unions. Instead, we are introducing a build plugin to generate the types of the routes for you based your file structure. This is similar to Nuxt and Vite Plugin Pages but with full type support (similar to nuxt-typed-router) while allowing you to keep using the exact same API, just with Autocompletion and typing hints 😄. The plugin currently supports Vite, Webpack (with some caveats), and rollup and it's currently experimental to gather feedback from the community and build a flexible solution. We hope to release a stable version in the following months.

Check out the plugin GitHub repository for installation instructions and documentation.

Here are some other examples of how much this plugin can improves your developer experience:

params validation in RouterLink Route infer from if condition Typed routes in navigation guards
CJS/MJS support for Node

We now expose a few extra entry points for Node but kept the old ones as well to prevent any disruption to the existing users. You can find more information about this in the corresponding pull request.


Please refer to CHANGELOG.md for details.

v4.0.16

Compare Source

Please refer to CHANGELOG.md for details.

v4.0.15

Compare Source

Please refer to CHANGELOG.md for details.

v4.0.14

Compare Source

Please refer to CHANGELOG.md for details.

v4.0.13

Compare Source

Please refer to CHANGELOG.md for details.

v4.0.12

Compare Source

Please refer to CHANGELOG.md for details.

v4.0.11

Compare Source

Please refer to CHANGELOG.md for details.

[v4.0.10](https://re

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • 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 renovate Bot added the 🤖 Automatic Issues/pull requests marked with this label were generated automatically by our helper bots. label Feb 1, 2026
@renovate

renovate Bot commented Feb 1, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ 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 error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: asf-config-web@1.0.0
npm error Found: vue@2.7.16
npm error node_modules/vue
npm error   vue@"2.7.16" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vue@"^3.5.34 || ^4.0.0" from vue-router@5.4.0
npm error node_modules/vue-router
npm error   vue-router@"5.4.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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-11-06T03_47_11_082Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-11-06T03_47_11_082Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch 2 times, most recently from 9b7d83b to c1c71f3 Compare February 5, 2026 15:11
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch 2 times, most recently from 750ada8 to e083091 Compare February 17, 2026 19:55
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch from e083091 to 1452eca Compare February 22, 2026 21:39
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch from 1452eca to 81685cf Compare March 5, 2026 19:49
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch from 81685cf to 1950d29 Compare March 13, 2026 12:07
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch from 1950d29 to 133e101 Compare March 22, 2026 16:38
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch from 133e101 to 4968afe Compare April 1, 2026 18:35
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch from 4968afe to 66744c3 Compare April 8, 2026 18:59
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch 3 times, most recently from 643fc81 to 41e9fc3 Compare April 29, 2026 16:10
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch 3 times, most recently from 98f2c75 to e3f22a9 Compare May 18, 2026 16:15
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch 3 times, most recently from 7de06d3 to 5c13a08 Compare June 1, 2026 23:04
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch from 5c13a08 to 2ed372c Compare June 11, 2026 12:56
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch 3 times, most recently from a63018a to b5662b2 Compare July 18, 2026 12:37
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch 2 times, most recently from 030a72b to e28b0ca Compare July 30, 2026 14:39
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch from e28b0ca to 37587d4 Compare August 12, 2026 01:15
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch from 37587d4 to e962510 Compare August 26, 2026 15:46
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch 4 times, most recently from 58fb033 to 01c7ca3 Compare September 5, 2026 14:32
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch from 01c7ca3 to b1aaa98 Compare September 7, 2026 23:47
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch from b1aaa98 to 141e376 Compare September 15, 2026 16:44
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch 2 times, most recently from 8d46d2e to cf4e31e Compare September 30, 2026 20:20
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch 2 times, most recently from c0cb45d to 0719c73 Compare October 10, 2026 16:48
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch 2 times, most recently from 32721b5 to 870ad30 Compare October 20, 2026 09:33
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch 2 times, most recently from 402d7e3 to 1063244 Compare October 26, 2026 16:25
@renovate
renovate Bot force-pushed the renovate/vue-router-5.x branch from 1063244 to 111c0d0 Compare November 6, 2026 03:47

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🤖 Automatic Issues/pull requests marked with this label were generated automatically by our helper bots.

Development

Successfully merging this pull request may close these issues.

1 participant