[Vue Router warn]: No match found for location with path "/_nuxt/__vite_ping"
See original GitHub issueEnvironment
- Operating System:
Windows_NT
- Node Version:
v16.14.2
- Nuxt Version:
latest
- Package Manager:
unknown
- Builder:
webpack
- User Config:
-
- Runtime Modules:
-
- Build Modules:
-
Reproduction
Can’t run after build project
Describe the bug
After I run npm run build
and npm run start
then I have a trouble
> start
> node .output/server/index.mjs
Listening on http://0.0.0.0:3000/
[Vue Router warn]: No match found for location with path "/_nuxt/__vite_ping"
[Vue Router warn]: No match found for location with path "/_nuxt/__vite_ping"
[Vue Router warn]: No match found for location with path "/_nuxt/__vite_ping"
I don’t know reason, it’s my package.json
{
"private": true,
"scripts": {
"dev": "nuxi dev",
"build": "nuxi build",
"generate": "nuxi generate",
"start": "node .output/server/index.mjs"
},
"devDependencies": {
"@intlify/nuxt3": "^0.1.10",
"@nuxt/types": "^2.13.2",
"@nuxt/typescript-build": "^2.1.0",
"@types/jquery": "^3.5.14",
"@vue/cli-plugin-typescript": "~5.0.0",
"@vue/eslint-config-prettier": "^6.0.0",
"@vue/eslint-config-typescript": "^10.0.0",
"eslint": "^8.14.0",
"eslint-plugin-vue": "^8.7.1",
"nuxt3": "latest",
"sass": "^1.50.0",
"sass-loader": "^12.6.0"
},
"dependencies": {
"@fortawesome/fontawesome-svg-core": "^6.1.1",
"@fortawesome/free-brands-svg-icons": "^6.1.1",
"@fortawesome/free-solid-svg-icons": "^6.1.1",
"@fortawesome/vue-fontawesome": "^3.0.0-5",
"@pinia/nuxt": "^0.1.8",
"@popperjs/core": "^2.11.5",
"@vueuse/core": "^8.3.1",
"bootstrap": "^5.1.3",
"express": "^4.18.0",
"gsap": "^3.10.4",
"jquery": "^3.6.0",
"nuxt-start": "^2.15.8",
"pinia": "^2.0.13",
"vue": "3.2.33",
"vue-router": "^4.0.14"
}
}
Additional context
No response
Logs
No response
Issue Analytics
- State:
- Created a year ago
- Comments:16 (5 by maintainers)
Top Results From Across the Web
[Vue Router warn]: No match found for location with path
I have defined the routes correctly I guess. Almost there. But it's not route : { route: "/login", name: "Login", component: Login, }....
Read more >[vue router warn]: no match found for location with path ...
On your main.js file try changing. const router = new VueRouter ( {routes}); to. const router = new VueRouter ( {routes, mode: 'history'});...
Read more >Using history mode with server side rendered templates raises ...
No matter what page I navigate to in my application, I always get warning to console "[Vue Router warn]: No match found for...
Read more >pages/ · Nuxt Directory Structure
This directory is optional, meaning that vue-router won't be included if you only ... routes will fail and you'll see that the route...
Read more >File System Routing - Nuxt
Unknown Dynamic Nested Routes. If you do not know the depth of your URL structure, you can use _.vue to dynamically match nested...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That’s your browser still requesting a URL which is accessible only in development (likely because you still have a hot-reloading browser tab open from development). Try closing all tabs in the browser first.
@bitkarrot You can uninstall the service worker registered to that host. This is not a Nuxt bug, just your browser requesting a resource that your Nuxt server is not serving.