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
I created a vue project using current @vue/cli package, then proceeded with vue add vuetify. When using the "Default" preset, the result works/looks fine. When using the "Prototype" or "Configure" preset, the end result fails with:
warning in ./src/plugins/vuetify.js
"export 'default' (imported as 'Vuetify') was not found in 'vuetify'
Or to be specific: It does not fail, but then a (visually) empty page seems to be served.
I compared the output of Default preset and the other presets and found that one difference is that the Default preset in src/plugins/vuetify.js does
import Vuetify from 'vuetify/lib';
and the other presets do
import Vuetify from 'vuetify';
Changing this made the warning go away, but when then opening up the page one gets a unstyled mess, so it still does not yield a working result. From here I could not determine what to change furthermore to get a proper starting result.
The text was updated successfully, but these errors were encountered:
julijane
changed the title
Only 'Default' preset generates a working result
Only 'Default' preset generates a usable result
Oct 20, 2019
I created a vue project using current @vue/cli package, then proceeded with
vue add vuetify
. When using the "Default" preset, the result works/looks fine. When using the "Prototype" or "Configure" preset, the end result fails with:Or to be specific: It does not fail, but then a (visually) empty page seems to be served.
I compared the output of Default preset and the other presets and found that one difference is that the Default preset in src/plugins/vuetify.js does
and the other presets do
Changing this made the warning go away, but when then opening up the page one gets a unstyled mess, so it still does not yield a working result. From here I could not determine what to change furthermore to get a proper starting result.
The text was updated successfully, but these errors were encountered: