Build and dev mode are slow and got errors in logs when importing Vuetify 3 with Vite-plugin-vuetify #15412

alexMugen · 2022-11-08T17:25:27Z

Environment

Operating System: Darwin
Node Version: v18.10.0
Nuxt Version: 3.0.0-rc.13
Nitro Version: 0.6.1
Package Manager: npm@8.19.2
Builder: vite
User Config: app, runtimeConfig, build, vite, imports, modules
Runtime Modules: (), @pinia/nuxt@0.4.3
Build Modules: -

Reproduction

Here the link of the stackblitz: https://stackblitz.com/edit/github-2wrsdj?file=nuxt.config.ts

I tried to clean and keep only the concerned code.

Below, the code that make the bug:

nuxt-config.ts

Describe the bug

Hello,

i have this logs on dev mode and build time, from rc-11 to the rc-13 ( _thanks a lot for your work by the way ) .
It make the build and the dev mode slow.

I don't know why, it seems like it doesn't find vuetify components on SSR during the build time and npm run dev.

When i start the dev, the rendering is good after hydration.

...
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VMain/VMain.sass"
...
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VPagination/VPagination.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VParallax/VParallax.sass"
...etc

Do you have any idea ? What i'm doing wrong ? I'm not sure this is a bug or a misunderstanding by me.
All the currents tuto on vuetify 3 / nuxt 3 just explain how to use it but none of them are talking about custom css that need to be import on vite:extendConfig

exemple https://www.the-koi.com/projects/how-to-set-up-a-project-with-nuxt3-and-vuetify3-with-a-quick-overview/

Hope there will be an official integration of vuetify 3 / nuxt 3

Thank you for your help.

Additional context

No response

Logs

[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:styles/main.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:styles/main.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:styles/main.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:styles/main.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VApp/VApp.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VApp/VApp.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VApp/VApp.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VApp/VApp.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VAppBar/VAppBar.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VAppBar/VAppBar.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VAppBar/VAppBar.sass"
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VAppBar/VAppBar.sass"

....

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

carlosmouracorreia · 2022-11-09T20:25:12Z

I'm having the same output/error and get 404 errors on the browser console when running npm run dev.

The error appears only when having a specific configuration file for styles - i.e, doesn't happen when pushing vuetify onto Vite plugins without arguments.

I followed the same tutorial and I'm not sure what's the correct way of importing vuetify via Vite yet, so it might be related.

maxcreation · 2022-11-10T14:04:53Z

I have the same issue.

I have https://my.local.app/_nuxt/%EF%BF%BDplugin-vuetify:components/VIcon/VIcon.sass not working. And many other components URLs broken like that. There seems to be this NULL byte after /_nuxt/ in the URL. And this https://my.local.app/_nuxt/plugin-vuetify:components/VIcon/VIcon.sass seems to work just fine. Also in the Nuxt dev yarn console I see same problem such files cannot be found/loaded. What adds this byte and how to get rid of it?

maxcreation · 2022-11-10T14:06:19Z

Maybe related to this? https://vitejs.dev/guide/api-plugin.html#virtual-modules-convention I got this from Kael.

mhfeizi · 2022-11-11T15:34:17Z

Disabling inlineSSRStyles fixed error for me.

https://v3.nuxtjs.org/api/configuration/nuxt-config#inlinessrstyles

maxcreation · 2022-11-13T20:46:26Z

@mhfeizi could you share how have you included Vuetify 3 in your Nuxt 3 project? With plugin? But what's in nuxt.config.ts and what's in the plugin file? Because it did not help me.

alexMugen · 2022-11-14T14:56:39Z

Disabling inlineSSRStyles fixed error for me.

https://v3.nuxtjs.org/api/configuration/nuxt-config#inlinessrstyles

It doesn't work for me
nuxt version => 3.0.0-rc.13

mhfeizi · 2022-11-14T17:51:10Z

@mhfeizi could you share how have you included Vuetify 3 in your Nuxt 3 project? With plugin? But what's in nuxt.config.ts and what's in the plugin file? Because it did not help me.

nuxt.config.ts

export const defaultConfigs = { 

ssr: true, 

experimental: { 

inlineSSRStyles: false 

}, 

vite: { 

ssr: { 

noExternal: ["vuetify"] 

} 

}, 

modules: [ 

(_options, nuxt) => { 

nuxt.hooks.hook( 

"vite:extendConfig", 

config => config.plugins?.push(vuetify({ styles: { configFile: "assets/vuetify.settings.scss" } })) as any 

); 

} 

] 

};

plugins/vueytify.ts

import { createVuetify } from "vuetify"; 

import { aliases, mdi } from "vuetify/iconsets/mdi-svg";


export default defineNuxtPlugin(app => { 

const vuetify = createVuetify({ 

ssr: true, 

icons: { 

defaultSet: "mdi", 

aliases, 

sets: { 

mdi 

} 

}

}); 

app.vueApp.use(vuetify); 

});

maxcreation · 2022-11-15T13:16:41Z

@mhfeizi thank you. Unfortunately, I still have the same errors in the Browser console and in the terminal. But your answer helped me understand and remove some of the misconfigurations I had. What do you have in assets/vuetify.settings.scss?

mgd216 · 2022-11-15T16:23:34Z

I'm using Nuxt 3.13 along with Vuetify 3.0.1 and also experiencing long load times in dev mode. Here is my plugins/vuetify.ts config that may help with some of the 404 component errors above:

import { createVuetify } from 'vuetify';
import * as components from 'vuetify/components';
import * as directives from 'vuetify/directives';
import { aliases, fa } from 'vuetify/iconsets/fa';
import colors from 'vuetify/lib/util/colors.mjs';

export default defineNuxtPlugin((nuxtApp) => {
  const vuetify = createVuetify({
    icons: {
      defaultSet: 'fa',
      aliases,
      sets: {
        fa,
      },
    },
    theme: {
      defaultTheme: 'dark',
      themes: {
        light: {
          dark: false,
          colors: {
            primary: colors.blue.darken2,
            secondary: colors.grey.darken3,
            accent: colors.blue.accent1,
            error: colors.red.accent2,
            info: colors.blue.base,
            success: colors.green.base,
            warning: colors.orange.darken1,
          },
        },
        dark: {
          dark: true,
          colors: {
            primary: colors.blue.darken4,
            secondary: colors.grey.darken1,
            accent: colors.pink.accent2,
            error: colors.red.darken2,
            info: colors.blue.base,
            success: colors.green.darken2,
            warning: colors.orange.darken1,
          },
        },
      },
    },
    components,
    directives,
  });

  nuxtApp.vueApp.use(vuetify);
});

The import * comopnents and * directives I think are key.

mhfeizi · 2022-11-16T17:16:29Z

What do you have in assets/vuetify.settings.scss?

@use 'vuetify/settings' with( /* ... */ );

maxcreation · 2022-11-16T18:42:24Z

Thanks. No clue then why not working for me. I disabled the plugin, but now I of course lack the ability to change vuetify Sass variables/settings per component. :(

…

On Wed, 16. Nov 2022 at 18:16, Mohammad Hosein Feizi < ***@***.***> wrote: What do you have in assets/vuetify.settings.scss? @use 'vuetify/settings' with( /* ... */ ); — Reply to this email directly, view it on GitHub <#15412>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAL33XQXWV3LDP7U4UU2UVDWIUJHRANCNFSM6AAAAAAR2SA2AQ> . You are receiving this because you commented.Message ID: ***@***.***>

mhfeizi · 2022-11-16T19:30:20Z

I also add vuetify.settings.scss in my main.scss and import main.scss in layout

main.scss

@use "./vuetify.settings.scss";

carlosmouracorreia · 2022-11-18T13:20:34Z

The problem is still here with Nuxt 3.0.0 stable right @alexMugen ? I got an email saying you fixed it but I assume you deleted the comment? Cheers

alexMugen · 2022-11-18T15:08:23Z

The problem is still here with Nuxt 3.0.0 stable right @alexMugen ? I got an email saying you fixed it but I assume you deleted the comment? Cheers

Yes it's still here unfortunately

YannFFT · 2023-01-16T14:30:23Z

Same issue here with Nuxt 3 stable version and Vuetify 3.1.1
It only happens when SSR is true

BayBreezy · 2023-01-20T09:05:13Z

Yeah, Vuetify 3.1.2 & Nuxt 3 showing errors in browser console when I customize SASS vars.
They only get displayed when ssr: true inside nuxt.config. I also cannot deploy the app to netlify because of the errors.

One of the many errors received: Failed to load resource: the server responded with a status of 404 (Page not found: /_nuxt/%EF%BF%BDplugin-vuetify:components/VAppBar/VAppBar.sass).

I don't know why this gets added %EF%BF%BD

mhfeizi · 2023-01-20T09:12:58Z

Temporary solution :

server/plugins/vuetify-fix.ts

export default defineNitroPlugin((nitroApp: any) => {
  nitroApp.hooks.hook("render:response", (response: any) => {
    response.body = response.body.replaceAll("/_nuxt/\0", "/_nuxt/");
  });
});

BayBreezy · 2023-01-20T10:09:16Z

Sadly I am not seeing where this changed anything.

Thanks tho.

BayBreezy · 2023-01-20T10:17:35Z

Temporary solution :

server/pluigns/vuetify-fix.ts

export default defineNitroPlugin((nitroApp: any) => {
  nitroApp.hooks.hook("render:response", (response: any) => {
    response.body = response.body.replaceAll("/_nuxt/\0", "/_nuxt/");
  });
});

Maybe this has something to do with the error? https://github.com/vuetifyjs/vuetify-loader/blob/next/packages/vite-plugin/src/stylesPlugin.ts#L227

ItsMeDelanoDev · 2023-01-20T21:56:21Z

Temporary solution :

server/pluigns/vuetify-fix.ts

export default defineNitroPlugin((nitroApp: any) => {
  nitroApp.hooks.hook("render:response", (response: any) => {
    response.body = response.body.replaceAll("/_nuxt/\0", "/_nuxt/");
  });
});

So you have it all working perfectly fine? I cannot get it to work, even with your suggestions in this thread.

So you don't have a very slow development environment, no toolbar/layout shifts the first seconds while it is loading?

If so, would it be possible for you to create a demo repository? That would be appreciated! I am currently doing some research towards Nuxt 3 compatible UI frameworks & libraries and would like to work with Vuetify.

BayBreezy · 2023-01-20T22:06:13Z

False alarm.. This actually worked!
It did not work initially because @mhfeizi wrote the folder name wrong.. instead of server/pluigns/vuetify-fix.ts , it should be server/plugins/vuetify-fix.ts. Plugins was spelt wrong. The errors are gone from the console. I will share a repo soon.

Thanks @mhfeizi

BayBreezy · 2023-01-21T06:07:32Z

@ItsMeDelanoDev here is the link to the repo with the customized variables working: https://github.com/BayBreezy/vuetify3-nuxt3-sass-customized

I also hosted it on Netlify with no trouble: https://v3customized.behonbaker.com/
Again, thanks @mhfeizi - That plugin saved me lol

KareemDa · 2023-01-21T16:34:37Z

@BayBreezy I'm trying your solution but I'm not getting the variables applied in the application!
do you have an idea why this happens ?

Here is my variables.scss:

When I replace vuetify/settings with vuetify: the basic sass variables work fine. but because I'm trying to
override a component sass variable "list" I'm getting a SASS error.

@BayBreezy Even when I tried to clone your repo, It seems not to work even locally. the font-family is "Roboto" instead of "Inter" !

coela-oss · 2023-10-08T02:21:34Z

@mostafaznv

With the upgrade to Vue3, Nuxt, Vuetify, and their surrounding libraries are still not aligned,
but as far as Vuetify is concerned, the reason is that almost all of them use vite-plugin-vuetify internally.

It is located in

https://github.com/vuetifyjs/vuetify-loader/blob/c4ead7300f63b702d96945440db6dd61835097dc/packages/shared/src/imports/getImports.ts#L24

Probably the most effective solution would be wait for this PR to be merged.

vuetifyjs/vuetify-loader#313

By the way, it can also be improved by replacing with a general-purpose plugin such as esbuild-sass-plugin instead of vite-plugin-vuetify.

I think many developers, myself included, don't understand that upgrading Vue3 and Nuxt3 involves fundamental changes.
It is supposed to be a more general-purpose and effective modification than before, but it seems that it is a modification that will lead to a decrease in development efficiency if it is tied to the existing source.

userquin · 2023-10-08T02:35:20Z

Probably the most effective solution would be wait for this PR to be merged.

vuetifyjs/vuetify-loader#313

I Will try to add those changes to vuetify nuxt module.

By the way, it can also be improved by replacing with a general-purpose plugin such as esbuild-sass-plugin instead of vite-plugin-vuetify.

I Will also try esbuild.

userquin · 2023-10-08T11:54:32Z

@coela-oss nice, esbuild sass plugin: precompile and precache. The styles once configured shouldn't change, why we need to rebuild them between dev server restarts?

coela-oss · 2023-10-08T17:07:25Z

@userquin
In this case, the reason is module has't updated in Vuetify3 loader that main stream changed to esbuild from webpack, not the expected behavior.

Vuetify3/Vite supports esbuild and TreeShaking, so loads only the necessary parts. They shouldn't have to look at the entire tree again and again if it worked according to specifications.

coela-oss · 2023-10-08T17:21:32Z

This is definitely not a Nuxt3 issue, but I need the docs how Nuxt2 absorbs Vue3 changes and separates Nuxi, Nitro, Vite, etc.

Please let me know if anyone has additional information. I may have overlooked something. Is this case's complexity, should be resolved by simply writing createVuetify and nuxtApp.vueApp.use(vuetify) in the plugin directory as Nuxt3?

TechAkayy · 2023-10-11T00:27:34Z

They are 2 completely different problems, the fact that sass is slow (I think this one has no solution) and the warnings in the sources

Anyone looking for Nuxt+Vuetify flavours, I have been doing a lot of trial & errors to setup some starter templates, and I have these three repos using this module (https://vuetify-nuxt-module.netlify.app/).

Based on my limited testing, these templates are not throwing any errors/warnings. All these repos build fine, so they include netlify demo urls.

Feel free to improve these templates by testing them at your end, and share them with the rest of us. Also, note that all three repos have a "blank" branch, which scaffolds just the project skeleton with an empty index.vue (just a single span), for a fresh start. Also, the tailwind & unocss ones use !important flag in their config to take precedence over the vuetify's generous use of !important.

As @userquin stated correctly, sass is slow, so these templates have sass override (for components) in nuxt.config.ts commented out. If you want to override component's sass variables, uncommented these two in the nuxt config file.

vuetify: {
    moduleOptions: {
      /* If customizing sass variables of vuetify components */
      /* If enabling this, set experimental.inlineSSRStyles to false */
      // styles: {
      //   configFile: 'assets/vuetify/settings.scss',
      // },
    },
    vuetifyOptions: './vuetify.config.ts', // This file is generally configured as configPath with Pinegrow Vuetify Plugin
},

  // Required when customizing Vuetify sass variables via configFile with SSR enabled - https://vuetify-nuxt-module.netlify.app/guide/server-side-rendering.html#vuetify-sass-variables
  // experimental: {
  //   inlineSSRStyles: false,
  // },

We will get there eventually!

itelmenko · 2024-03-05T11:13:23Z

Temporary solution :

server/plugins/vuetify-fix.ts

export default defineNitroPlugin((nitroApp: any) => {
  nitroApp.hooks.hook("render:response", (response: any) => {
    response.body = response.body.replaceAll("/_nuxt/\0", "/_nuxt/");
  });
});

This works fine. But it need restart server for applying.

Question. Why it does not work out of box in Nuxt?

danielroe · 2024-03-05T18:29:56Z

Can you provide a minimal reproduction?

itelmenko · 2024-03-06T09:05:28Z

Can you provide a minimal reproduction?

https://github.com/itelmenko/nuxt3-vuetify3-customisation

In browser dev console I see a lot of errors:

....

 WARN  Sourcemap for "plugin-vuetify:components/VSlideGroup/VSlideGroup.sass" points to missing source files                                                  11:50:54 AM

.....
[Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VApp/VApp.sass"

npm_run_dev.log

If I add server plugin

 mv server.backup server
 npm run dev

then I don't see errors in browser console, I dont see [Vue Router warn]: No match found for location with path "/_nuxt/%EF%BF%BDplugin-vuetify:components/VApp/VApp.sass" in linux console (terminal). But I see errors like WARN Sourcemap for "plugin-vuetify:components/VSlideGroup/VSlideGroup.sass" points to missing source files still.

mostafaznv · 2024-03-06T18:54:12Z

But I see errors like WARN Sourcemap for "plugin-vuetify:components/VSlideGroup/VSlideGroup.sass" points to missing source files still.

You can disable Nuxt's source map option.

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

Combining these two workarounds might resolve the issue, but it's somewhat a messy solution.

Unfortunately, the Vuetify team has no plans to maintain support for their official nuxt-vite plugin, and the Nuxt team doesn't seem inclined to do so either.

On the other hand, NuxtUI is not as feature-rich as Vuetify "yet". So, we, as Vue users, find ourselves navigating this endless desert alone, hoping for a day when either NuxtUI or PrimeVue will step up to take on the responsibility.

I’m feeling a bit tired, but at the same time, I’m filled with hope and readiness. I believe the switch to one of them will happen at some point this year.

danielroe · 2024-03-06T19:12:13Z

If there’s something we can fix in Nuxt, we will. (which is why I asked for a reproduction.) But as far as I’m aware these stem from issues with Vuetify.

also note there is an excellent module by @userquin which solves these issues for Nuxt users.

itelmenko · 2024-03-06T19:41:24Z

also note there is an excellent module by @userquin which solves these issues for Nuxt users.

Could you explain what do you mean? What solution exactly?

danielroe · 2024-03-06T22:01:54Z

@itelmenko any chance you could make it a minimal reproduction? 🙏

BayBreezy · 2024-03-06T23:11:16Z

@itelmenko I think Daniel is referring to this module here: https://vuetify-nuxt-module.netlify.app/

It gets rid of some of the issues posted above. I was so frustrated with the Vuetify + Nuxt integration that I created my own UI lib here: https://ui-thing.behonbaker.com/getting-started/introduction

itelmenko · 2024-03-07T04:59:56Z

@itelmenko any chance you could make it a minimal reproduction? 🙏

#15412 (comment)

Or what do you mean?

danielroe · 2024-03-07T09:38:38Z

It's quite a big project: https://github.com/itelmenko/nuxt3-vuetify3-customisation/blob/main/package.json#L12-L27

Here's more about what I mean by a minimal reproduction

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
👉 https://codesandbox.io/s/github/nuxt/starter/v3-codesandbox

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

SvenjaReissaus · 2024-03-09T05:51:53Z

Will this work?

https://github.com/SvenjaReissaus/nuxt-vuetify-sass

mostafaznv · 2024-03-09T05:55:19Z

Will this work?

https://github.com/SvenjaReissaus/nuxt-vuetify-sass

I recommend using this: https://github.com/userquin/vuetify-nuxt-module.
It's still in beta versions, but it works quite well.

SvenjaReissaus · 2024-03-09T22:52:45Z

Will this work?
https://github.com/SvenjaReissaus/nuxt-vuetify-sass

I recommend using this: https://github.com/userquin/vuetify-nuxt-module. It's still in beta versions, but it works quite well.

I feel adding a third-party module to an issue reproduction might just add an extra layer of where the issue is originated from. Are you able to reproduce the issue using that module?

itelmenko · 2024-03-14T10:32:17Z

I recommend using this: https://github.com/userquin/vuetify-nuxt-module. It's still in beta versions, but it works quite well.

There is not enough documentation.
I don't see how can I define

Vuetify globals
Vuetify custom themes
Vuetify sass variables (reefine)

Could you send some snippets?

daniandl · 2024-03-14T10:33:32Z

Please move this discussion to the third party module, it is not relevant to this issue

itelmenko · 2024-03-14T10:39:03Z

It's quite a big project: https://github.com/itelmenko/nuxt3-vuetify3-customisation/blob/main/package.json#L12-L27

Here's more about what I mean by a minimal reproduction

Do you mean minimal reproduction with userquin/vuetify-nuxt-module or without it?

userquin · 2024-03-21T02:14:39Z

Here my pr vuetifyjs/vuetify-loader#332

Nuxt reproduction there (link to open the repo in stackblitz in the readme file) using a local vite plugin tgz, you can remove the dependency and add the vuetify plugin and run the dev:sourcemap script.

Right now we also have some vue router warnings in nuxt.

The problem, vite will not show the sourcemap map. The missing source warnings is because entries in sources array in the sourcemap with file:/// prefix.

TechAkayy · 2024-06-06T02:16:30Z

Just in case anyone missed this 🥇

YourItalianChef · 2024-08-19T15:47:12Z

finally it is resolved
Thanks

userquin · 2024-09-05T14:05:32Z

Check vuetifyjs/vuetify-loader#338 , there are links to Vite and Nuxt repos, check the corresponding branch.

vuetify-nuxt-module works even with SASS Variables on SSR without any missing source warnings: updating SASS variables also working (HMR).

Anyone using Vuetify should switch to modern SASS compiler, update vite to latest 5.4.3 version (>= 5.4.0) and replace sass with sass-embedded. Using latest Vite doesn't need to change the configuration to include the new modern SASS compiler.

Check these videos (can be found in Vuetify discord server in nuxt channel):

Vuetify Nuxt module with modern sass compiler and sass variables: https://www.youtube.com/watch?v=aamWg1TuC3o
Same with Vuetify $utilities turned-off and using UnoCSS instead: https://www.youtube.com/watch?v=tIN7yAQwGTs

alexMugen added the pending triage label Nov 8, 2022

alexMugen changed the title ~~Build and dev mode are slow when importing Vuetify 3~~ Build and dev mode are slow when importing Vuetify 3 with Vite-plugin-vuetify Nov 8, 2022

alexMugen changed the title ~~Build and dev mode are slow when importing Vuetify 3 with Vite-plugin-vuetify~~ Build and dev mode are slow and got errors in logs when importing Vuetify 3 with Vite-plugin-vuetify Nov 8, 2022

carlosmouracorreia mentioned this issue Nov 10, 2022

Setting custom SASS variable often fails (using vite) vuetifyjs/vuetify-loader#273

Open

carlosmouracorreia mentioned this issue Dec 2, 2022

SassError: Can't find stylesheet to import. vuetifyjs/vuetify-loader#276

Open

danielroe added the 3.x label Jan 19, 2023

danielroe transferred this issue from nuxt/framework Jan 19, 2023

TechAkayy mentioned this issue Oct 11, 2023

Unable to Use Vuetify Sass Variables vuetifyjs/nuxt-module#115

Closed

danielroe removed the 3.x label Jun 30, 2024

This comment was marked as duplicate.

Sign in to view

This comment was marked as off-topic.

Sign in to view

Build and dev mode are slow and got errors in logs when importing Vuetify 3 with Vite-plugin-vuetify #15412

Build and dev mode are slow and got errors in logs when importing Vuetify 3 with Vite-plugin-vuetify #15412

Comments

alexMugen commented Nov 8, 2022 • edited Loading

Environment

Reproduction

Describe the bug

Additional context

Logs

carlosmouracorreia commented Nov 9, 2022 • edited Loading

maxcreation commented Nov 10, 2022

maxcreation commented Nov 10, 2022

mhfeizi commented Nov 11, 2022

maxcreation commented Nov 13, 2022 • edited Loading

alexMugen commented Nov 14, 2022 • edited Loading

mhfeizi commented Nov 14, 2022

maxcreation commented Nov 15, 2022

mgd216 commented Nov 15, 2022 • edited Loading

mhfeizi commented Nov 16, 2022

maxcreation commented Nov 16, 2022 via email

mhfeizi commented Nov 16, 2022

carlosmouracorreia commented Nov 18, 2022

alexMugen commented Nov 18, 2022

YannFFT commented Jan 16, 2023 • edited Loading

BayBreezy commented Jan 20, 2023

mhfeizi commented Jan 20, 2023 • edited Loading

BayBreezy commented Jan 20, 2023

BayBreezy commented Jan 20, 2023

ItsMeDelanoDev commented Jan 20, 2023 • edited Loading

BayBreezy commented Jan 20, 2023

BayBreezy commented Jan 21, 2023

KareemDa commented Jan 21, 2023 • edited Loading

coela-oss commented Oct 8, 2023

userquin commented Oct 8, 2023

userquin commented Oct 8, 2023 • edited Loading

coela-oss commented Oct 8, 2023

coela-oss commented Oct 8, 2023

TechAkayy commented Oct 11, 2023 • edited Loading

itelmenko commented Mar 5, 2024

danielroe commented Mar 5, 2024

itelmenko commented Mar 6, 2024 • edited Loading

mostafaznv commented Mar 6, 2024 • edited Loading

danielroe commented Mar 6, 2024

itelmenko commented Mar 6, 2024

danielroe commented Mar 6, 2024

BayBreezy commented Mar 6, 2024

itelmenko commented Mar 7, 2024 • edited Loading

danielroe commented Mar 7, 2024

Why do I need to provide a reproduction?

What will happen?

How can I create a reproduction?

SvenjaReissaus commented Mar 9, 2024

mostafaznv commented Mar 9, 2024

SvenjaReissaus commented Mar 9, 2024

itelmenko commented Mar 14, 2024

daniandl commented Mar 14, 2024

itelmenko commented Mar 14, 2024

userquin commented Mar 21, 2024 • edited Loading

TechAkayy commented Jun 6, 2024

This comment was marked as duplicate.

This comment was marked as off-topic.

YourItalianChef commented Aug 19, 2024

userquin commented Sep 5, 2024 • edited Loading

alexMugen commented Nov 8, 2022 •

edited

Loading

carlosmouracorreia commented Nov 9, 2022 •

edited

Loading

maxcreation commented Nov 13, 2022 •

edited

Loading

alexMugen commented Nov 14, 2022 •

edited

Loading

mgd216 commented Nov 15, 2022 •

edited

Loading

YannFFT commented Jan 16, 2023 •

edited

Loading

mhfeizi commented Jan 20, 2023 •

edited

Loading

ItsMeDelanoDev commented Jan 20, 2023 •

edited

Loading

KareemDa commented Jan 21, 2023 •

edited

Loading

userquin commented Oct 8, 2023 •

edited

Loading

TechAkayy commented Oct 11, 2023 •

edited

Loading

itelmenko commented Mar 6, 2024 •

edited

Loading

mostafaznv commented Mar 6, 2024 •

edited

Loading

itelmenko commented Mar 7, 2024 •

edited

Loading

userquin commented Mar 21, 2024 •

edited

Loading

userquin commented Sep 5, 2024 •

edited

Loading