"No match found for location with path" is still spammed on unknown paths about nuxt.js

[danielroe]

The issue in v3.12.1 is hopefully resolved in #27487 and should be in the next patch.

Workaround for prod apps:

For now, you can try working around the issue in production by explicitly setting NODE_ENV=production when running your app.

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• github-hmpfds (Open reproduction)

[ChinDer]

I'm having this problem too.

[danielroe]

I will investigate this. For now, you can try working around the issue in production by explicitly setting NODE_ENV=production when running your app.

[roaa-alrajabi]

We are having this issue on production as well, not just on dev environment

[tymon42]

Same problem.

[danielroe]

If you are having the problem on production, even with explicitly setting NODE_ENV, would you please provide a reproduction? 🙏

[husayt]

I get this problem when switching compatibilityVersion: 4, with nuxt 3.12.1 on windows

[rylanharper]

I'm getting the same issue on my Nuxt sites using the Shopify Graphql API (using the Nuxt GraphQL Client module) upon upgrading to Nuxt ^3.12.1. I get the same [Vue Router warn] error messages shown above when navigating to each route (except pointing to my graphql client when referencing the "location"). I also see I have the following warning as well:

plugin.mjs:8 [nuxt] Could not access `graphql-client`. The only available runtime config keys on the client side are `public` and `app`. See `https://nuxt.com/docs/guide/going-further/runtime-config` for more information.`

[toniengelhardt]

Also seeing this in v3.12.1.

Not sure if related, but I'm using public runtime config var for the URLs like

<NuxtLink :to="$config.public.urls.docsUrl">Docs</NuxtLink>