-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nuxt Layers Cannot find module 'vuetify/package.json' #277
Comments
Try adding vuetify as dependency |
Adding vuetify in parent project does fixes error, but now it ignores all configuration, like SASS variables $color-pack: false, |
what's your project structure? I don't see any layer in the configuration nor custom modules |
i encountered similar problem, where the base layer locates in the same level of the project extending this layer (instead of layer folder inside the project) so in the project package.json , does it have to include vuetify-nuxt-module as dependency (base-layer already has included) nuxtprojects/base-layer/nuxt.config.ts export default defineNuxtConfig({
modules: ['vuetify-nuxt-module']
}) nuxtprojects/project/nuxt.config.ts export default defineNuxtConfig({
extends: ['../base-layer']
}) |
Hi everyone, I encountered this problem and found that removing the options from the resolve method resolved the issue. Everything is now working correctly. Change this: function resolveVuetifyBase() {
return path.dirname(require.resolve("vuetify/package.json", { paths: [process.cwd()] }));
} To this: function resolveVuetifyBase() {
return path.dirname(require.resolve("vuetify/package.json"));
} |
Hello! Tried to use vuetify-nuxt-module in layer and include it in parent project, got error while running yarn dev:
Function that causes error
node_modules/.c12/gitlab_ecofinance_frontend_3egwiQ38Rj/node_modules/@vuetify/loader-shared/dist/index.mjs
Parent nuxt config:
Layer nuxt config:
Adding same vuetify-nuxt-module dependency in parent project fixes problem, but it rewrites all layer config.
The text was updated successfully, but these errors were encountered: