Reputation: 384
When I load vuetify via the vue-cli3, I get an error when i do npm run serve, saying there is a missing loader.
Docs etc and searches have come up blank.
This is a fresh project, no code loaded. Just following the instructions from the vuetify site.
Can anyone help?
Upvotes: 9
Views: 24777
Reputation: 2572
I had the same problem. This whole thing worked out for me.
vue create your-app
cd your-app
npm i --save-dev --no-optional vuetify-loader vue-cli-plugin sass node-sass sass-loader
npm i
vue add vuetify
I know this looks redundant but it worked.
Upvotes: 1
Reputation: 638
just install the pacakge to devDependencies:
npm i --save-dev vue-loader-v16
After installing the dev dependency
npm run serve
Upvotes: 0
Reputation: 1
In your package.json
: move @nuxtjs/vuetify
from devDependencies
to dependencies
Upvotes: 0
Reputation: 1
do a npm install
after adding vuetify as vue add vuetify
then start server by
npm run serve
Upvotes: 0
Reputation: 73
you should check the vue-loader plugin path. in my case it is:
vue-loader/dist/plugin
Upvotes: 3
Reputation: 1381
Try to manually install the package:
npm install vuetify-loader -D
Upvotes: 8
Reputation: 97
I've got the same issues while creating new Vuetify app by official guide.
After adding vuetify: vue add vuetify
The missing step was installing new npm dependencies with: npm install
Later I run npm run serve
and it started succesfully.
There is an issue in the documentation!
Upvotes: 8
Reputation: 1203
Just had the same problem. In my case it was caused by placing the file vue.config.js in the top-level-folder (next to package.json) instead of in the 'src' folder. Obviously there might be many reasons for this error, but maybe it helps someone...
Upvotes: 0
Reputation: 22714
I got the same error when I cloned a repository and I installed the dependencies only on the master branch. When I switched to a different branch (git checkout different_branch
) I forgot to install the dependencies there. So make sure you installed the dependencies before you launch the server.
Upvotes: 0
Reputation: 302
Run npm cache clean --force
. It should clear your npm cache.
For reference: https://github.com/npm/npm/issues/19072#issuecomment-345555468
Upvotes: 2