migrating from v0.14 to v0.15-beta.12
Wanted to upgrade to v0.15-beta.12 my existing quasar project (currently 0.14.7).
Bumped the version in package.json, did npm install, then npm run dev.
Got the error straight away:
These dependencies were not found:
- quasar in ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/App.vue, ./src/main.js and 13 others
- quasar/dist/quasar.ie in ./src/main.js
- quasar/dist/quasar.ie.mat.css in ./src/main.js
To install them, you can run: npm install --save quasar quasar/dist/quasar.ie quasar/dist/quasar.ie.mat.css
Well, I went to my main.js and commented out IE11 support to see if that helps:
// IE11 Support
Then did npm run dev again:
This dependency was not found:
- quasar in ./src/main.js, ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/App.vue and 13 others
To install it, you can run: npm install --save quasar
Hm, this seems to be a bit weird as quasar package (npm info quasar) has nothing to do with the quasar-framework package that is being used.
Is there anyone that did actually manage to migrate from an old (v0.14) version of quasar to v0.15?
This might be a silly question but did you also update to the v0.15 quasar-cli (npm install -g quasar-cli@next)?
I suggest you wait for the docs. You will not be able to upgrade in the way you tried, and you won’t be able to copy your src folder either, so best wait for the migration guide. That or install the new cli, init a new project, a move files one by one, carefully, respecting the new structure.
Docs are being written as we speak
@ryan nope, I didn’t
maybe I could give it a try
I’m waiting for the final 0.15 release to migrate my 0.14 project. I have quite a few webpack tweaks (loaders, custom output directories etc.), will it be possible to do them in the vue-cli-based Quasar v0.15? I would appreciate a section about that in the docs.
@benoitranque Hi, is there a way to follow the progress on v0.15? I’d be very interested in getting an approximate timeframe for its release (for my planning purposes). Thanks for all the work.