Quasar Edge points to v0.14 beta now
-
Hi All,
If you are using edge version, please switch to latest official v0.13.10 release instead. Edge is becoming v0.14 and due to tree shaking it will break your app.
Thank you.
-
Attempting to start a new project now with 0.14 and here is what I see if I
quasar init app_name
cd app_name
npm install
rm -rf node_modules/quasar-framework
npm i --save git+https://git@github.com/quasarframework/quasar-edge.gitI see this
“UNMET PEER DEPENDENCY quasar-extras@0.x”quasar dev
In the js console I see:
“[Vue warn]: Unknown custom element: <q-layout>”
“[Vue warn]: Unknown custom element: <q-toolbar-title>”[HMR] bundle has 2 warnings
client.js?7955:161 ./~/babel-loader/lib!./~/vue-loader/lib/selector.js?type=script&index=0!./src/components/Index.vue
45:32-37 "export ‘Utils’ was not found in ‘quasar’
./~/babel-loader/lib!./~/vue-loader/lib/selector.js?type=script&index=0!./src/components/Index.vue
49:34-39 "export ‘Utils’ was not found in ‘quasar’
“Uncaught TypeError: Cannot read property ‘dom’ of undefined”If I then run:
npm install quasar-extras --save
quasar devThe unmet dependency is fixed, but I see the same things in the console.
Just checking to see if you are aware of these or if I’m taking the wrong path to using the beta.
-
I just noticed the other post mentioned the extras: http://forum.quasar-framework.org/topic/507/v0-14-beta-important-notice
And I see I have “quasar-extras”: “0.0.7” after installing it.
-
This post is deleted! -
@smakinson you should use the beta template for init
first make sure you have the latest quasar-cli version installed : npm install -g quasar-cli
then use this to start your project:quasar init default#beta app_name
the rest of your procedure looks good and should yield a functional project.
-
Ah thanks for that! I did update the cli first, but did not notice I needed default#beta.