Start v0.15 project -> upgrades
-
if i use 0.14?
-
@snezhkois Check your version with “quasar version” in your project.
-
Quasar CLI v0.6.4
App running on Quasar v0.14.7 -
This post is deleted! -
@snezhkois Yes, your app is on 0.14
-
to get started with v0.15 :
npm install -g quasar-cli@next quasar init -
@benoitranque said in Start v0.15 project -> upgrades:
npm install -g quasar-cli@next
i see that i must replace all my code in new version
-
How can I start with quasar-cli electron or android with 0.15?
-
Can I just update quasar without init new project?
-
@snezhkois Not if you are updating from v0.14, as there are major breaking changes.
@bestog
quasar build --helpis all the info you need
-
Thanks. Hope other updates will not so “hard”
-
@benoitranque Thank you. I was blind.
-
@snezhkois They won’t be, you’ll just have to
npm update quasar-framework -
Unfortunatly I have an error, the same after two tryouts. If you wonder what happens in a normal cmd window (instead of powershell) it’s the same. This is windows 10 64bit machine. Also I just pressed ENTER with the cordova question (I don’t want it actually). Any tips?
[EDIT] I see by default there is not a ‘scripts’ entry for ‘dev’ in ‘package.json’ I’ll see if I need to make that. I though since there is src it would show something with ‘quasar dev’ just like ‘quasar test’ works
PS D:\Workspace…\chk\chk> quasar dev
D:\Workspace…\chk\chk\node_modules\quasar-cli\bin\quasar-dev:60
async function goLive () {
^^^^^^^^
SyntaxError: Unexpected token function-
module.js:20 require
internal/module.js:20:19 -
quasar:80 Object.<anonymous>
[chk]/[quasar-cli]/bin/quasar:80:3
-
-
Make sure you install the latest version of quasar-cli by selecting the next branch.
npm install -g quasar-cli@nextedit:
Also note you must have node version 8+
-
ah then the node must be the issue. I’ll try tonight
