Open marvin-j97 opened 4 years ago
This might actually be a problem with Vuetify itself and maybe is related to https://github.com/vuetifyjs/vuetify/issues/9938
Could be nice to know if it's reproducible with https://github.com/nuxt-community/vuetify-module/releases/tag/v2.0.0-alpha.1
Overall I think there's nothing we can do, it's some Vuetify CSS order issue...
Upstream => vuetifyjs/vuetify#9938 Not something the Nuxt module can fix, unless never use treeShaking at all but means performance issue in production.
I guess https://github.com/nuxt-community/vuetify-module/issues/208#issuecomment-564503274 is a workaround (but performance issue)
For the record, I'm experiencing no transitions in production as well—specifically with the default (or any other transitions) with my dialogs. I just transitioned my project over from using Vue CLI to using Nuxt and my transitions were working just fine in Vue CLI (which was obviously not using the vuetify-module). Now, using Nuxt and the vuetify-module, transitions are not working. Same version of vuetify used both ways.
Module version 1.9.1
Describe the bug Vuetify animations (e.g. v-fade-transition, v-expand-transition, ...) are not rendered in production mode (npm run build && npm start).
To Reproduce https://github.com/dotvirus/nuxt-vuetify-animation-bug
Steps to reproduce the behavior:
Expected behavior Animations should look like the ones when running "npm run dev".