-
-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"No match found for location with path" is still spammed on unknown paths #26947
Comments
Start a new pull request in StackBlitz Codeflow. |
I'm having this problem too. |
I will investigate this. For now, you can try working around the issue in production by explicitly setting |
We are having this issue on production as well, not just on dev environment |
This comment was marked as duplicate.
This comment was marked as duplicate.
If you are having the problem on production, even with explicitly setting |
I get this problem when switching compatibilityVersion: 4, with nuxt 3.12.1 on windows |
I'm getting the same issue on my Nuxt sites using the Shopify Graphql API (using the
|
Also seeing this in Not sure if related, but I'm using public runtime config var for the URLs like <NuxtLink :to="$config.public.urls.docsUrl">Docs</NuxtLink> |
The issue in v3.12.1 is hopefully resolved in #27487 and should be in the next patch. Workaround for prod apps:
|
Environment
Basically everywhere, on my windows development machine:
And in the production docker image using node-20 / node-21 alpine where I can only provide the nitro.json:
Reproduction
Basically a new project from the template using the vue-router and a page, but for the sake of simplicity:
https://stackblitz.com/edit/github-hmpfds?file=app.vue
Describe the bug
Relates #26425 + #26519
If I understood correctly the issue should be resolved by using the latest nuxt build, but doesn't seem to: When visiting an unknown route - even if having an error.vue in root - the message
[Vue Router warn]: No match found for location with path
is printed several times (I couldn't find a correlation between the amount of pages and log entries, sometimes it seems to be 4 times, other times it's about 15x). That happens in the development environment, and in the production build.Additional context
The Dockerfile building the production image:
Logs
The text was updated successfully, but these errors were encountered: