In production build the server console is full of vue router warns for /_nuxt/

[twin geode]

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

Seems to be the same issue as this guy but I don't see any resolution
#💬・discussion message

How am I meant to debug router warnings anyhow?

[grave torrent]

Hi @twin geode. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

---

Based on the knowledge sources provided, I don't have enough specific information to directly address the issue of Vue Router warnings for "/_nuxt/" paths in a production build. However, I can provide some general guidance on debugging router warnings in Nuxt and offer a potential workaround.

For debugging router warnings in Nuxt, you can refer to the Nuxt debugging documentation. This guide suggests several approaches:

1. Enable sourcemaps for better debugging:

export default defineNuxtConfig({
  sourcemap: {
    server: true,
    client: true
  }
})

2. Use the Node inspector for server-side debugging:

nuxi dev --inspect

3. Set up debugging in your IDE, such as VS Code or JetBrains IDEs, using the configurations provided in the documentation.

As for the specific issue with Vue Router warnings, while I don't have a direct solution, there's a potential workaround that might help reduce similar warnings. In a GitHub issue discussion about removing __NUXT__ after hydration, it was mentioned that you can access the payload using useNuxtApp().payload instead of window.__NUXT__ GitHub PR #27745. This change might help reduce some router-related warnings, although it's not directly addressing your specific issue.

If these approaches don't resolve your issue, you might want to consider:

1. Checking if your routes are correctly defined in your Nuxt configuration.
2. Ensuring that all your components and pages are properly imported and registered.
3. Verifying that there are no conflicts between your client-side and server-side routing.

If the problem persists, it would be helpful to create a minimal reproduction of the issue and share it on the Nuxt GitHub repository for further assistance from the community or the Nuxt team.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: