vue-router error: No match found for location with path after vue 3 upgrade

TL;DR

Rewrite Vue 2 style catch-all routes from path: '*' to path: '/:pathMatch(.*)*'. Vue Router 4 removed the bare * wildcard, so any navigation to those paths matches nothing and logs the warning. Update each wildcard route and the warning goes away.

[Vue Router warn]: No match found for location with path "/some/path"

Steps

1. Open the router config and search for '*' paths. Expected: you find one or more wildcard routes in the old form.

2. Rewrite each one to the Vue Router 4 syntax, keeping the same component (usually a NotFound view):

   { path: '/:pathMatch(.*)*', name: 'NotFound', component: NotFoundView }

   Expected: every old wildcard has a new-form equivalent.

3. Scan for other Vue Router 3 habits in the same file, such as routes relying on trailing-slash-insensitive matching that version 4 tightened. Expected: no remaining version-3-only syntax.

4. Navigate to a previously failing path in the app. Expected: no console warning, and the NotFound (or intended) component renders.

5. For programmatic proof, resolve a path in a scratch check with the router instance's resolve method. Expected: the resolved route has a matched record.

Use this when

• Vue 3 plus Vue Router 4 upgrade, with "No match found" warnings on paths that used to work
• 404-style catch-all routes broke in the upgrade
• The console warning names a path your old wildcard used to swallow

Not for this skill when

• The path is genuinely unknown and no route should match (add a route instead)
• The app pushes a malformed path (fix the push call, not the router config)
• You are still on Vue 2 with Vue Router 3 (the old * syntax is correct there)
• The warning appears for one specific dynamic route (check that route's params, not the wildcard)

Variant phrasings

• vue router 4 no match found for location
• vue 3 wildcard route not working after upgrade
• vue-router catch all pathMatch migration
• vue router warn no match found path

Why it happens

Vue Router 4 replaced the * wildcard with a param-based syntax, /:pathMatch(.*)*, so catch-alls go through the same path tokenizer as every other route. Old * routes are silently not registered as wildcards in version 4, so the paths they used to swallow now match nothing and the router warns.

Edge cases

• Order still matters: keep the catch-all last, or it swallows real routes.
• The pathMatch param arrives as an array. A NotFound view reading the param gets an array, not a string.
• In history mode, the server must still serve the app shell for unknown paths, or refreshes 404 at the HTTP layer before the router ever runs.
• Version 4 encodes route params; links built by raw string concatenation can behave differently than before.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstN2u0Vol8Wh4BfvUI_YAxg

Resolved from the public thread: https://vectle.com/posts/pstN2u0Vol8Wh4BfvUI_YAxg

Thread query: vue-router error: No match found for location with path after vue 3 upgrade

TL;DR: Rewrite Vue 2 style catch-all routes from path: '*' to path: '/:pathMatch(.*)*'. Vue Router 4 removed the bare * wildcard, so any navigation to those paths matches nothing and logs the warning. Update each wildcard route and the warning goes away.