vue-router
5.5.1 · 13 Nov 2026MIT13.4M / weekRepositoryHomepagenpmAtom feed
151 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 5.x · latest line
5.5.1
13 Nov 2026Summary· from the note as AI read it
Read before upgrading: 1 change to make.
- Breaking
experimental: Avoid full stack traces for match misses
Breaking Changes
- Breaking
experimental: Avoid full stack traces for match misses
Features
Warn on repeatable params being passed as scalars
experimental: Warn on relative object locations before the initial navigation
experimental: Add RouterLink and useLink for experimental_createRouter
Bug Fixes
Escape - by 36eee12 [( in s)](github.com/vuejs/router/commit/ in static path tokens (#2897))
experimental: Resolve relative object locations against the current route
experimental: Display location on its own line in VUE_ROUTER_R0129
history: Keep userinfo by using relative urls in pushState
matcher: Refine param separator matching
unplugin: Read quoted keys in definePage() at build time
5.5.0
10 Nov 2026Summary· from the note as AI read it
Nothing to change: 5 new, 23 fixed.
Features
Warn on colliding query with params
experimental: Customize scroll restoration capture listeners
experimental: Export default scroll capture listener setup
experimental: Support type safe route record props
scroll-restoration: Make capture triggers configurable
unplugin: Declare route params in defineProps() with definePage props true
volar: Type defineProps() with route params when definePage props is true
volar: Add typedDefineProps option to sfc-typed-router
Bug Fixes
Avoid replaceState on pagehide if scrollRestoration is manual
Fallback to useId for vapor
Preserve named-view props and detect quoted props keys
Keep non-object props when merging
experimental: Match root paths with multiple optional params
experimental: Remove query param set to undefined
experimental: Keep query value for params omitted from params
experimental: Compare query values element by element in R0123
matcher: Avoid exponential backtracking on .* repeatable params
router-view: UseRoute() returns the route prop in descendants
router-view: Handle pending async component roots in onRouteRendered
scroll: Save scroll positions in sessionStorage instead of history.state
scroll: Keep scroll positions in memory when sessionStorage fails
scroll: Ignore invalid scroll positions in sessionStorage
scroll-restoration: Overwrite parent capture and restore
scroll-restoration: Reserve keys for pending async pages
scroll-restoration: Restore position after native hash links
types: Add hotUpdateCallback to auto-resolver handleHotUpdate
types: Accept classic parseQuery in RouterOptions
types: Allow undefined on push for query params with default
unplugin: Support definePage with webpack and rspack
unplugin: Keep aliased named imports in definePage extraction
unplugin: Reload pages with stale route props
Performance
Strip build-time definePage properties
unplugin: Watch page files only in dev server
5.4.0
7 Oct 2026- Breaking
experimental: Normalize query values to arrays
Accept a prebuilt matcher in
createRouterUseScrollRestoration and onRouteRendered
Breaking Changes
- Breaking
experimental: Normalize query values to arrays
Features
Accept a prebuilt matcher in
createRouterUseScrollRestoration and onRouteRendered
Diagnose experimental beforeEnter migration
experimental: Warn about legacy optional param removal
experimental: Extract hash params with definePage
experimental: Configure required and default hash params
experimental: Never decode the hash, protect-only encoding
experimental: Allow custom regexp for path params in definePage
router: Restore hashes and top by default
Bug Fixes
Resolve experimental guard redirects against target on history navigation
experimental: Keep declared case of static prefix in MatcherPatternPathStar.build()
experimental: Make hash params optional and nullable
experimental: Exclude defaults from required hash params
experimental: Align hash parameter parsing with queries
experimental: Keep last hash param instead of throwing
experimental: Disallow required with a default for query params
experimental: Make query params with a default optional on push
experimental: Do not inherit params, query, or hash on redirects
history: Invalidate obsolete scroll positions
unplugin: Sanitize named view in definePage import
unplugin: Keep hex character codes in param segments regexp
Performance
unplugin: Cache merged route overrides
5.3.1
2 Sep 2026experimental: Handle non-string params for isActive
5.3.0
27 Aug 2026Prevent race condition dev-only error
scroll: Skip scroll computation based on history.scrollRestoration
unplugin: Don't crash on duplicate definePage() calls
Features
Prevent race condition dev-only error
scroll: Skip scroll computation based on history.scrollRestoration
unplugin: Don't crash on duplicate definePage() calls
volar: Narrow
typeof useRoutein a type context
Bug Fixes
history: Remove visibilitychange listener to prevent focus steal in Edge
router: Skip scroll saving for unknown pop direction
types: Allow unsetting a route name with
falseinEditableTreeNodeunplugin: Sort and dedupe params in generated types
unplugin: Skip unnamed params in generated route types
unplugin: Report unnamed params once per route
unplugin: Generate param types from override paths and stop inheritance on absolute overrides
Performance
Replace
json5andyamlwithconfboxAvoid depending on the current route to resolve absolute locations
experimental: Avoid tracking currentRoute in absolute string locations
5.2.0
15 Jul 2026Add helpful diagnostics
Allow pinia 4
scroll: Ignore stale async scrollBehavior results
Features
Add helpful diagnostics
Bug Fixes
Allow pinia 4
scroll: Ignore stale async scrollBehavior results
unplugin: Reject invalid hex digits in [x+hh] character codes
5.1.0
28 May 2026Typed definePage params.path
Strict type for definePage param default
Support raw param parsers
Features
Typed definePage params.path
Strict type for definePage param default
Support raw param parsers
Force array type raw param parsers
Allow overriding the global Router type
Emit runtime warning for invalid format in query params
Override useRouter() return with experimental types config
Allow string as a param parser for convenience
Bug Fixes
Fix auto import fixes and make experimental esm only
Deterministic param parser types order
Avoid importing unused param parsers
Filter invalid query params without failing to match
Detect not set format
Allow undefined values for params in query
experimental: Repeatable params in subsegments
types: Add vite as optional peer dependency
5.0.7
13 May 2026- Security
query: Use Object.create(null) to prevent prototype pollution
Upgrade to babel 8
Make
defineParamParser()more intuitive
Features
Upgrade to babel 8
Make
defineParamParser()more intuitiveUpgrade
@vue/devtools-apimatcher: Hint at
params: {}workaround in discarded params warningparam-parsers: Add include/exclude options
Bug Fixes
matcher: Finalize param token before processing escaped colon
- Security
query: Use Object.create(null) to prevent prototype pollution
resolve: Omit empty optional params from resolved params
types: Wire RouteNamedMap via generated routes.d.ts
unplugin: Avoid generating empty routes
unplugin: Apply definePage path-param parser overrides
volar: Drop runtime
@vue/language-coreimport
5.0.6
22 Apr 2026Missing closing quote in generated import
5.0.5
22 Apr 2026Enable standard schema param parsers
Normalize param parsers once
Track definePage imports per-file to fix named view race condition
Features
Enable standard schema param parsers
Normalize param parsers once
Bug Fixes
Track definePage imports per-file to fix named view race condition
Avoid double decoding hash on string location
5.0.4
19 Mar 2026Avoid iterator helpers for Node 20 compat
Escape backslahes in string literals
Avoid false duplicate route warning for named views
Bug Fixes
Avoid iterator helpers for Node 20 compat
Escape backslahes in string literals
Avoid false duplicate route warning for named views
Allow pushing to auto routes
loaders: Restore context in sequential awaits
5.0.3
19 Feb 2026- Breaking
experimental: Make miss() throw internally and return never
- Breaking
experimental: Add reroute() and deprecate NavigationResult
- Breaking
experimental: Remove selectNavigationResult
Breaking Changes
- Breaking
experimental: Make miss() throw internally and return never
- Breaking
experimental: Add reroute() and deprecate NavigationResult
- Breaking
experimental: Remove selectNavigationResult
Features
Support _parent in nested folders
Warn on _parent conflict
Set _parent as non matchable by default
Warn on conflicting components for routes
Use type module
- Deprecated
Add deprecation warning for next() callback in navigation guards
Extract alias from definePage
Display aliases in logs
- Deprecated
Deprecate new NavigationResult(to) in favor of reroute(to)
experimental: Handle aliasOf in resolvers
experimental: Generate aliases from override in resolver
experimental: Warn against non absolute aliases
Bug Fixes
Avoid non matchable routes in auto-routes
Handle quotes in d.ts
Avoid route entry in map for _parent
Handle nested groups
Stable route ordering for group folders with same path
Correct route ordering for group nodes with inflated scores
Cleanup old route overrides
Remove name from _parent.vue files
experimental: Resolve TS errors in resolver/router type hierarchy
types: Relax RouteMapGeneric constraint for interface-based RouteNamedMap
volar: Use
ts.getTokenPosOfNodeinstead ofnode.getStart
Performance
Avoid merging empty object in record
5.0.2
2 Feb 2026Remove devtools from iife build
Loose version check vue-router
volar: Empty options
5.0.1
30 Jan 2026volar: Make typed plugin work with vue-tsc
5.0.0
29 Jan 2026experimental: Query params are optional by default
Add volar plugins
Add data loaders as experimental
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-apibecause 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
Add volar plugins
Add data loaders as experimental
Add route json schema
Runtime error on missing param parsers
volar: Allow rootDir option
Bug Fixes
Avoid breaking older browsers support
Trigger navigation guards when keep-alive component is reactivated for different route
Add automatic types for param parsers
Param parsers when dts is not at root
Expose resolveOptions for unplugin
Escape tildes in paths
volar: Upgrade config read
- 4.x
4.6.5
13 Nov 2026Escape - by ae8c4b3 [( in s)](github.com/vuejs/router/commit/ in static path tokens (#2897))
matcher: Refine param separator matching
4.6.4
11 Dec 2025experimental: Handle redirect types
experimental: Basic alias
Make the build output compatible with v4.5
Features
experimental: Handle redirect types
experimental: Basic alias
Bug Fixes
Make the build output compatible with v4.5
experimental: IsActive with custom params
4.6.3
16 Oct 2025Reinstate ESM browser builds
4.6.0
14 Oct 2025A new experimental Custom resolvers features, meant to replace in the future the current implementation but partially introduced through
vue-router/experimental. Meant to be used in combination withunplugin-vue-routerfor the moment. Still lacking documentationrouterlink: allow event handlers under strictTemplates (fix #2484)
router: use pagehide for iOS navigation
This release refactors the build to use
tsup. Please report any issue you may find regarding to types or incorrectly unresolved exportsThere is a new
vue-router/experimentalexport which is used mainly byunplugin-vue-routerwith the new custom resolvers that bring a smaller router runtime, faster route matching, custom param types and matching on query parameters. There is still some work to do so the API is still experimental and may change in future releases. If you want to give it a try, check the experimental playground in unplugin-vue-router. If you use file based routing, this will be a transparent upgrade for you (in the future). Currently it still lacks a couple of features likealiasand dynamic routing.Features
A new experimental Custom resolvers features, meant to replace in the future the current implementation but partially introduced through
vue-router/experimental. Meant to be used in combination withunplugin-vue-routerfor the moment. Still lacking documentation
Bug Fixes
routerlink: allow event handlers under strictTemplates (fix #2484)
router: use pagehide for iOS navigation
types: missing options in RouteLocationGeneric
Performance Improvements
parseURL minor improvements
4.5.1
25 Apr 2025Memory history stores state
types: add support for children routes as union
Missing viewTransition prop on RouterLink
4.5.0
25 Nov 2024link: add view-transition prop
Throw if parent and child routes have the same name
Combining 'end' and 'strict'
Features
link: add view-transition prop
Throw if parent and child routes have the same name
Bug Fixes
Combining 'end' and 'strict'
Custom directive doesn't work when custom=true
router: allow duplicated navigation on back + redirect
4.4.5
13 Sep 2024Fix mods in aliases
Make internal property non enumerable
Mods must be added only wiht defineProperty
4.4.4
10 Sep 2024loaders: internal mods in route records
ssr: handle symboless Modules in dynamic imports
4.4.3
6 Aug 2024Reorder exports in
package.json
4.4.1
31 Jul 2024warn: fix links to docs
Router typescript definations related to vue package
types: stricter meta with required fields
4.4.0
21 Jun 20244.3.3
10 Jun 2024Use a binary search for insertMatcher
4.3.2
18 Apr 2024Revert "fix: avoid normalizing the fullPath (#2189)" (b78aa98), closes vuejs/router#2216
4.3.1
17 Apr 2024dx: warn when
addRoutecannot find the parentdx: warn when passing undefined/null locations
Avoid normalizing the fullPath (#2189) (c54fc84), closes vuejs/router#2187
4.3.0
21 Feb 2024Allow auto types
Check document for browser instead of window
Features
Allow auto types
Bug Fixes
4.2.5
22 Sep 2023devtools: display children with empty parent (d7af338), closes posva/unplugin-vue-router#235
4.2.4
6 Jul 2023Allow removing guards within the guard
4.2.3
5 Jul 2023Use getter instead of
computedfor route location
4.2.2
29 May 20234.2.1
18 May 2023types: revert declare module vue
4.2.0
11 May 2023Allow inject within global navigation guards
warn: improve infinite redirect warning message
Features
Allow inject within global navigation guards
warn: improve infinite redirect warning message
Bug Fixes
4.1.6
24 Oct 2022matcher: avoid empty records to be reached
types: improve link and view slots
4.1.4
22 Aug 20224.1.3
27 Jul 2022Avoid restore on cancelled pop navigations
4.1.2
11 Jul 2022types: simplify props types
Allow requiring in cjs context
Force relativse link in types exportcs
Features
types: simplify props types
Bug Fixes
Allow requiring in cjs context
Force relativse link in types exportcs
types: adds ESM export of types
types: allow
symboltype
4.1.0
4 Jul 2022We 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.
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/componentsoption in routesIt's now possible to completely omit the
componentoption when defining routes with children. While nested routes are about defining layouts, they are also directly connected to apathand users often found themselves defining a pass through component that would just render a<RouterView>component to reuse thepathstructure. 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 astateproperty when callingrouter.push()orrouter.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
stateproperty.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
stateproperty.Given the nature of the
<RouterView>'srouteprop, there is also a new functionloadRouteLocation()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
pathproperty, creating autocomplete and type safety inrouter.push()and<RouterLink>'stoprop. 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.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.