@quasar/cli - undefined
-
Re: Trying to upgrade: 'Quasar App Extension "upgrade" is missing'
I’m no longer able to upgrade Quasar in my project:
$ quasar info Operating System - Darwin(20.3.0) - darwin/x64 NodeJs - 12.20.2 Global packages NPM - 6.14.11 yarn - Not installed @quasar/cli - undefined @quasar/icongenie - 2.3.3 cordova - Not installed Important local packages quasar - 2.0.0-beta.5 -- Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time @quasar/app - 3.0.0-beta.7 -- Quasar Framework local CLI @quasar/extras - 1.9.17 -- Quasar Framework fonts, icons and animations eslint-plugin-quasar - Not installed vue - 3.0.5 -- vue vue-router - 4.0.3 -- This is the repository for Vue Router 4 (for Vue 3) vuex - 4.0.0 -- state management for Vue.js electron - Not installed electron-packager - Not installed electron-builder - Not installed @babel/core - 7.12.16 -- Babel compiler core. webpack - 4.44.1 -- Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff. webpack-dev-server - 3.11.0 -- Serves a webpack app. Updates the browser on changes. workbox-webpack-plugin - Not installed register-service-worker - 1.7.1 -- Script for registering service worker, with hooks typescript - 4.1.3 -- TypeScript is a language for application scale JavaScript development @capacitor/core - Not installed @capacitor/cli - Not installed @capacitor/android - Not installed @capacitor/ios - Not installed Quasar App Extensions *None installed* $ quasar upgrade App · Looking for Quasar App Extension "upgrade" command App · ⚠️ Quasar App Extension "upgrade" is missing...
I had the same problem a couple of weeks ago and managed to fix it using the following commands:
npm -g cache clean --force npm -g cache verify npm cache clean --force npm cache verify npm -g uninstall @quasar/cli npm -g install @quasar/cli npm uninstall @quasar/cli rm -fr node_modules rm package-lock.json npm i
but now it doesn’t seem to have any effect.
I’m on macOS Big Sur v11.2.1 and all the above commands are run in iTerm2, NOT a terminal inside my editor.
What else can I try to fix the problem?
Thanks.
-
@archimede said in @quasar/cli - undefined:
You could try the macos default terminal.
-
@dobbel thanks so much for the suggestion: it actually works in the Terminal app.
But now I have to ask: why? I’ve always used iTerm2 (also, but not only, for this project) and never had issues like this one. Any idea what might be wrong with Quasar/iTerm2?
Btw, closing iTerm2 and reopening it also works.
Cheers.
-
Sorry no idea.