Vuetify-module: Nuxt throw error when updating to the latest version

[jefrydco]

Module version
1.7.0

Describe the bug
Running the latest version throws an error

To Reproduce

Upgrade the module to the latest version and nuxt building progress will throw an error as shown in the screen capture below.

Expected behavior
No error appeared.

Screenshots

Additional context
-

[assoft]

I have the same problem

[kevinmarrec]

Working on a fix, sorry for the inconvenience

[kevinmarrec]

Please try 1.7.1 and ping me if it's correctly fixed.

[udanpe]

Please try 1.7.1 and ping me if it's correctly fixed.

Not work for me.
Error: Template src not found: @nuxtjs/vuetify/dist/templates/plugin.js
but current path /@nuxtjs/vuetify/templates/plugin.js

[kevinmarrec]

@udanpe Can you try replacing
node_modules@nuxtjs/vuetify/dist/build.js L27

path.join(__dirname, '../templates', 'options.js')

by

path.resolve(__dirname, '../templates', 'options.js')

?

[kevinmarrec]

Nvm though you had options issue, but it's around plugin you have issue, but I don't understand why.

path.resolve(__dirname, '../templates', 'plugin.js')

should point to @nuxtjs/vuetify/templates/plugin.js

[kevinmarrec]

@udanpe I'm not sure you updated to last version, your error is from 1.7.0 and you're using custom options, so it was only failing on plugin (not options).

I'm not able to reproduce the issue locally unfortunately

[kevinmarrec]

My website https://marrec.io is hosted on Netlify and is using this module, and just bumping the new version fixed it for me:

[udanpe]

@kevinmarrec after replace to resolve everything works.
1.7.0 does not have templates folder. it's really 1.7.1.
npm remove --save @nuxtjs/vuetify && npm i -D @nuxtjs/[email protected]

UPD 1. macOS + node 12
UPD 2. in addition i use typescript \ nuxt-ts

[kevinmarrec]

Relased 1.7.2 but I think I've published without building 🤦‍♂️, should be fine with : 1.7.3 then now

[kevinmarrec]

@udanpe Clean up and reinstall dependencies, you seem to have a broken node_modules

[udanpe]

@kevinmarrec Thanks. After removing node_modules, package-lock and reinstall everything works.