Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Upgrading to 1.5.1 from 1.2.7

See original GitHub issue

Describe the bug

I had the following versions:

“quasar”: “^1.2.7” “@quasar/extras”: “^1.2”

I ran the following commands:

npm install quasar@latest
npm install @quasar/extras@latest

Expected behavior Everything should work fine.

What really happened

Platform (please complete the following information): OS: Win 10 Node: 12.13.0 NPM: 6.12.0

Issue Analytics

State:
Created 4 years ago
Comments:8 (3 by maintainers)

Top GitHub Comments

1reaction

MartinManevcommented, Nov 28, 2019

There is a problem with Vue CLI 3 where a cache is created in node_modules/.cache and that cache does not invalidate when you update your dependencies. Can you try deleting this folder and running your app again? Here is the original issue: https://github.com/vuejs/vue-cli/issues/4438

Vue CLI 4 is out and I think the issue is fixed but I haven’t verified it myself yet.

0reactions

rstoenescucommented, Dec 9, 2019

For Vue CLI 4 use vue-cli-plugin-quasar v2+. Due to a bug in Vue CLI (v3 for sure, might have been fixed in v4), it is required that you clean up cache. Not Quasar’s fault. Quasar is added to the transpileDependencies list automatically by the vue-cli-plugin-quasar.