You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Webpack + postcss has been working pretty well for us, giving us the ability to scope any and all css in any given app to a specific selector, including the main Vuetify stylesheet. We noticed, however, that vuetify generates a stylesheet at run-time with an id of "vuetify-theme-stylesheet." Unfortunately this bypasses our postcss config at build-time and thus overwrites any existing styles with the same name.
Proposed solution
Add the ability to scope the "vuetify-theme-stylesheet" stylesheet to a specific selector. Perhaps an option during...
Problem to solve
Webpack + postcss has been working pretty well for us, giving us the ability to scope any and all css in any given app to a specific selector, including the main Vuetify stylesheet. We noticed, however, that vuetify generates a stylesheet at run-time with an id of "vuetify-theme-stylesheet." Unfortunately this bypasses our postcss config at build-time and thus overwrites any existing styles with the same name.
Proposed solution
Add the ability to scope the "vuetify-theme-stylesheet" stylesheet to a specific selector. Perhaps an option during...
Ideally we wouldn't need to declare the selector twice (once in our postcss config and another in Vue.use()).
The text was updated successfully, but these errors were encountered: