Weird vue router warnings on cold start #150

daniandl · 2023-11-10T15:38:00Z

Thanks for trying to tackle all these Nuxt<>Vuetify issues with this library.

I pretty much copied the playground setup with the configFile variant, because I want to customize the components.
It works fine, the hydration time and cold start time is a bit longer, but that's normal, as Vuetify docs said.

However, the server and client logs print this:

ℹ Vite server warmed up in 1447ms                                             4:21:32 PM
ℹ Vite client warmed up in 1668ms                                             4:21:32 PM
✔ Nitro built in 352 ms                                                 nitro 4:21:32 PM
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VAppBar/VAppBar.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VAppBar/VAppBar.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VAppBar/VAppBar.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VAppBar/VAppBar.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VImg/VImg.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VImg/VImg.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VImg/VImg.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VImg/VImg.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VApp/VApp.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VApp/VApp.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VApp/VApp.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VApp/VApp.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VToolbar/VToolbar.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VToolbar/VToolbar.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VToolbar/VToolbar.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VToolbar/VToolbar.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VBtn/VBtn.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VBtn/VBtn.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VBtn/VBtn.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VBtn/VBtn.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VBtnGroup/VBtnGroup.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VBtnGroup/VBtnGroup.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VBtnGroup/VBtnGroup.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VBtnGroup/VBtnGroup.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VIcon/VIcon.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VIcon/VIcon.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VIcon/VIcon.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VIcon/VIcon.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/@plugin-vuetify/lib/components/VResponsive/VResponsive.sass"
... many more components :)

Just thought I'd document it, it's not really causing any issues (as far as I can tell).
Almost seems its the same issue we had to patch in the nitro response, except now its in vue router...

The text was updated successfully, but these errors were encountered:

userquin · 2023-11-10T17:45:05Z

@daniandl we're checking what's the change in Nuxt, it is working properly in 3.8.0

userquin · 2023-11-12T13:59:34Z

@daniandl I'm going to release a new minor (breaking) updating to latest Nuxt (3.8.1), @nuxt/kit (2.8.1), Vite (4.5.0) and Vuetify (3.4), it seems there are some internal breaking changes in Nuxt (I guess it is about types), tests on my local works without any sass router warnings/errors (dev tools still with /@vite/client warnings/errors)

EDIT: seems to be there when using Node 18, on my local using Node 20.9.0 , cannot reproduce it (here an SB repro, using Node 18: https://stackblitz.com/edit/userquin-vuetify-nuxt-module-wzhs9k?file=playground%2Fnuxt.config.mts)

TouchSek · 2023-11-21T03:49:22Z

Same issue.

userquin · 2023-11-22T18:46:12Z

The next minor will not solve the error (linked PR): nuxt/cli#188

hermes85pl · 2024-09-07T17:16:40Z

For me, when using Node v20.15.0, with this module in version 0.15.2 the issue is not present, and I do experience it after switching to 0.16.1 (having all the other dependencies in the latest version).

userquin · 2024-09-07T18:09:22Z

can you try using latest 0.18.2 replacing sass with sass-embedded (1.77.8)? it would be better to update also to latest Nuxt 3.13.* and Vite 5.4.3 (maybe you need to use resolutions or overrides in your package.json for Vite) that solves a lot of sass issues: the issue is about the sass resolver.

You can check vuetifyjs/vuetify-loader#338, there are links to 2 PR with custom Vite plugin and custom Nuxt module (using SASS variables with and without SSR), checkout the corresponding branch (logic missing in main branch in both repositories)

hermes85pl · 2024-09-07T18:19:44Z

When I update to 0.18.2, I get other error instead, upon loading a page from the dev server (anonymized):

[8:15:20 PM]  ERROR  Internal server error: [sass] Error: ENOENT: no such file or directory, open '/.../node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/vuetify/lib/styles/main.sass?direct'
  ╷
2 │ @use "file:///.../node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/vuetify/lib/styles/main.sass%3Fdirect"
  │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
  file:///@vuetify-styles/lib/styles/main.sass 2:1  root stylesheet
  Plugin: vite:css
  File: /@vuetify-styles/lib/styles/main.sass:2:1
  Error: Error: ENOENT: no such file or directory, open '/.../node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/vuetify/lib/styles/main.sass?direct'
    ╷
  2 │ @use "file:///.../node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/vuetify/lib/styles/main.sass%3Fdirect"
    │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ╵
    file:///@vuetify-styles/lib/styles/main.sass 2:1  root stylesheet
      at handleCompileResponse (/.../node_modules/.pnpm/[email protected]/node_modules/sass-embedded/lib/src/compiler/utils.ts:221:11)
      at AsyncCompiler.compileRequestAsync (/.../node_modules/.pnpm/[email protected]/node_modules/sass-embedded/lib/src/compiler/async.ts:136:33)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at compileStringAsync (/.../node_modules/.pnpm/[email protected]/node_modules/sass-embedded/lib/src/compile.ts:54:12)


 WARN  [Vue Router warn]: No match found for location with path "/_nuxt/@vuetify-styles/lib/styles/main.sass"

I am not willing to experiment with resolutions or overrides to stay on the edge; instead, I will wait for things to stabilize and update in a normal way, so for now I am sticking to 0.15.2.

userquin · 2024-09-07T18:47:35Z

Try removing the node_modules/.vite folder beware it is .vite not vite or run pnpm dedupe.

hermes85pl · 2024-09-07T20:28:03Z

This was after a clean installation, without .vite there; pnpm dedupe did not help either.

userquin · 2024-09-07T22:41:53Z

@hermes85pl is your repo public? If not, can you provide the nuxt config file?

theAvocadoCoder · 2024-09-13T13:50:22Z

I've also encountered this issue, using Nuxt 3.13.1 and vuetify-nuxt-module 0.18.2 ( and Node 20.15.1)

I got a lot of Vue Router warnings for all the Vuetify components I use in the app and ENOENT errors for the components' Sass files. Setting nuxt to 3.10.0 and vuetify-nuxt-module to 0.15.2 got rid of the server log errors as far as I can tell but there are still errors in my console when I open dev tools on my browser.

I'm open to troubleshooting this so I've made a branch in my project with the modules set to their latest versions. I've tried replacing sass with sass-embedded and also used overrides to set vite to 5.4.3. That didn't change the errors I was getting. I should note that I'm very new to Nuxt and have not worked extensively with Sass either.

I've made my repo public.

userquin · 2024-09-13T14:52:09Z

@theAvocadoCoder I'm going to do some changes:

write sass files to temporary files, will solve all the problems
update logic to always configure the modern SASS compiler: right now using Vite defaults when Vite >= 5.4.2

I'll test your repo with pkg-pr-new from the new PR I'm preparing, I hope release v0.18.3 today once tested.

NOTE: I cannot use npm in your repo, getting weird error about rollup binary, I'm testing it with pnpm on my local.

userquin · 2024-09-13T15:32:48Z

@theAvocadoCoder seems to be working now, these are the dependencies (vuetify-nuxt-module from this PR #278, tested on Nuxt 3.13.1 and 3.12.4).

can you update your vnm-troubleshoot dependencies and check it 🙏?

"dependencies": {
    "@nuxt/devtools": "^1.3.14",
    "@pinia/nuxt": "^0.5.4",
    "mongodb": "6.8",
    "nuxt": "^3.13.1",
    "pinia": "^2.2.2",
    "vite": "^5.4.5",
    "vue": "latest",
    "vuetify": "^3.7.1"
  },
  "devDependencies": {
    "@nuxtjs/tailwindcss": "^6.12.1",
    "sass-embedded": "^1.78.0",
    "vuetify-nuxt-module": "https://pkg.pr.new/vuetify-nuxt-module@278"
  },
  "overrides": {
    "vue": "latest",
    "vite": "^5.4.5"
  }

theAvocadoCoder · 2024-09-13T15:42:15Z

I'm not sure why the npm error happened, I use npm on my local. I've tested and this works. No errors or warnings related to the module in my browser console or the server logs and the styles are loading as they should. Thanks!

userquin · 2024-09-13T15:43:07Z

@theAvocadoCoder thx, releasing v0.18.3, I'll ping you here when released

userquin · 2024-09-13T15:50:10Z

@theAvocadoCoder v0.18.3 released, change the vuetify-nuxt-module to ^0.18.3 and install dependencies, should be fixed

theAvocadoCoder · 2024-09-13T15:56:02Z

Yup! It is. Thankss

TechAkayy · 2024-09-14T02:30:07Z

Just a note, I was able to avoid the npm error by adding the package throwing error as an optionalDependencies in my package.json, something to do with npm itself.

  "optionalDependencies": {
    "@rollup/rollup-darwin-arm64": "*"
  }

daniandl changed the title ~~Weird warnings on cold start~~ Weird vue router warnings on cold start Nov 10, 2023

userquin mentioned this issue Nov 12, 2023

fix!: #app module augmentation and types #156

Merged

userquin mentioned this issue Dec 22, 2023

No match found for location with path... #171

Closed

userquin mentioned this issue Sep 13, 2024

fix(sass): remove query params when resolving virtual sass modules #278

Merged

theAvocadoCoder mentioned this issue Sep 13, 2024

Vnm troubleshoot theAvocadoCoder/daily-bingo#1

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Weird vue router warnings on cold start #150

Weird vue router warnings on cold start #150

daniandl commented Nov 10, 2023

userquin commented Nov 10, 2023

userquin commented Nov 12, 2023 •

edited

Loading

TouchSek commented Nov 21, 2023

userquin commented Nov 22, 2023

hermes85pl commented Sep 7, 2024

userquin commented Sep 7, 2024 •

edited

Loading

hermes85pl commented Sep 7, 2024 •

edited

Loading

userquin commented Sep 7, 2024

hermes85pl commented Sep 7, 2024

userquin commented Sep 7, 2024 •

edited

Loading

theAvocadoCoder commented Sep 13, 2024

userquin commented Sep 13, 2024 •

edited

Loading

userquin commented Sep 13, 2024 •

edited

Loading

theAvocadoCoder commented Sep 13, 2024

userquin commented Sep 13, 2024

userquin commented Sep 13, 2024

theAvocadoCoder commented Sep 13, 2024

TechAkayy commented Sep 14, 2024

Weird vue router warnings on cold start #150

Weird vue router warnings on cold start #150

Comments

daniandl commented Nov 10, 2023

userquin commented Nov 10, 2023

userquin commented Nov 12, 2023 • edited Loading

TouchSek commented Nov 21, 2023

userquin commented Nov 22, 2023

hermes85pl commented Sep 7, 2024

userquin commented Sep 7, 2024 • edited Loading

hermes85pl commented Sep 7, 2024 • edited Loading

userquin commented Sep 7, 2024

hermes85pl commented Sep 7, 2024

userquin commented Sep 7, 2024 • edited Loading

theAvocadoCoder commented Sep 13, 2024

userquin commented Sep 13, 2024 • edited Loading

userquin commented Sep 13, 2024 • edited Loading

theAvocadoCoder commented Sep 13, 2024

userquin commented Sep 13, 2024

userquin commented Sep 13, 2024

theAvocadoCoder commented Sep 13, 2024

TechAkayy commented Sep 14, 2024

userquin commented Nov 12, 2023 •

edited

Loading

userquin commented Sep 7, 2024 •

edited

Loading

hermes85pl commented Sep 7, 2024 •

edited

Loading

userquin commented Sep 7, 2024 •

edited

Loading

userquin commented Sep 13, 2024 •

edited

Loading

userquin commented Sep 13, 2024 •

edited

Loading