karma-phantomjs-shim | Provides shims when running tests in PhantomJS | Development Tools library

What year did you create your Vue.js project? Your package.json look like old and Vuetify Installation need your project updated.

I recommend that you create a new project with Vue CLI (with last version), install Vuetify and then migrate your files from the old project for the new project.

It's seems a hard work, but is very simple.

Use also the last version of Node.js.

In my point of view, there was internet connection trouble, so packages didn't downloaded properly. Issue was solved by reinstalling Vue.js and other packages.

The vue.config.js file is only used when using the vue-cli-service. If you are using Vue CLI 3 or higher, it should create a project without any visible webpack configuration. Instead, the vue-cli-service will look for a vue.config.js file to configure your build.

In your case you are using an older version. Your webpack configuration is inside the build folder, as hinted by your package.json. Your build folder should contain three files, namely webpack.base.conf.js, webpack.dev.conf.js and webpack.prod.conf.js. The base file is used for both environments. The dev file is used for your dev server (when you run npm run dev). The prod file is used for production (when you build your application using npm run build). Modify these files to get the behaviour you want.

Never had your problem so I don't know if this will help, but:

The problem is that this some sort of pre-built starter project, and the developer made some decisions which you don't fully understand yet.

Since this strategy has frustrated you, I recommend trying a different strategy: build the simplest possible project that you possibly can, using as few libraries as possible, and build out from there. Good luck!

Can you try to add template part:

This is happening because when a PWA is installed and opened on a phone it rewrites the URL to /index.html whereas the vuetify app is rendered at /.

Just re-adjust your vue-router to load the component at /index.html too and it should work.

Your router.js could look something like this:

You're using an incorrect target:

I used avoriaz to fix my problem, and through mount method I could inject the component dependency.

MyComponent.spec.js