Quasar Upgrade is failing due to npm server error on MAC
While trying to upgrade quasar on macOS PC, with
quasar upgrade --installit is resulting in following error:
Quasar CLI · Gathering information with yarn... @quasar/extras: 1.3.2 → Skipping! (⚠️ NPM server returned an error, so we cannot detect latest version) quasar: 1.1.6 → Skipping! (⚠️ NPM server returned an error, so we cannot detect latest version) @quasar/app: 1.4.3 → Skipping! (⚠️ NPM server returned an error, so we cannot detect latest version) Congrats! All Quasar packages are up to date.
Note: I have installed quasar cli with npm, hence yarn package manager is not present.
I have exactly the same problem but on Windows 10. I also have installed Quasar with npm (as shown in the docs) and do not have yarn installed.
Is Quasar working with npm? If not, then why is not this mentioned in the docs?
I guess there might be some regression going on since @rstoenescu fixed something that seems related in 1.0.0-beta7 - https://github.com/quasarframework/quasar/releases/tag/%40quasar%2Fcli-v1.0.0-beta.7
Found the problem - there was an old yarn.lock file in the project dir and the quasar upgrade script checks for its existence in order to decide which packager to use.
Removed it and now everything works.
Sorry for the false alarm!
@ddenev glad that you figured it out
cristiano.moraes last edited by cristiano.moraes
I am getting the same problem reported here but I used Yarn instead, to install Quasar. Removing yarn.lock file and install yarn again make no difference. Any ideas?
dobbel last edited by dobbel
Yarn instead, to install Quasar.
No that’s not the recommended way:
npm for global packages -> quasar cli, vue cli, grunt cli , ect.
yarn for project packages -> quasar app ,quasar extra’s, everything in package.js under
dependencies. Most of under
cristiano.moraes last edited by
Thank you for your answer @dobbel. I did what you suggested and it is working now.