Closed kimini507 closed 4 years ago
Hi,
Cannot reproduce. Please provide more information. What terminal are you using? Did you try to delete node_modules and yarn.lock/package-lock.json and yarn/npm installl again?
I just created a new project and am also unable to reproduce -- works perfectly fine. I am on Ubuntu 18.04.
Hi guys, sorry for the late response, just came back to work.
I added additional information on the post above. Also I'm using powershell @rstoenescu .
There's something wrong with my environment and I can't pinpoint what. Upgrade to 1.4.3 works in my colleague's machine.
@hawkeye64 , looked at the two issues you shared.
More info: Right now in my repo, the @quasar/app
version is 1.4.0
and 1.4.2
(i have 2 projects with the same issue)
@quasar/cli
is 1.0.5
The quasar
command successfully sees my directory as a quasar app before upgrade. But after running quasar upgrade -i
and it upgrades my @quasar/app
to 1.4.3
, quasar dev
or quasar -h
shows the message:
--------------
=> IMPORTANT !
=> Trigger this inside of a Quasar project (and npm/yarn install) for more commands.
--------------
Right now I'm sticking to the current version where it's working.
Are you inside a corporate network? can you check what is inside node_modules/@quasar
subfolders? you might have some bullshit returned with a 200 response code by a filtering proxy.
Hi @pdanpdan , sadly I'm not inside a corporate network.
Here's what's inside the node_modules/@quasar
:
Mode LastWriteTime Length Name
---- ------------- ------ ----
d----- 07/01/2020 12:20 PM app
d----- 07/01/2020 12:20 PM babel-preset-app
d----- 07/01/2020 12:20 PM extras
d----- 07/01/2020 12:20 PM fastclick
d----- 07/01/2020 12:24 PM quasar-app-extension-icon-genie
d----- 07/01/2020 12:20 PM quasar-app-extension-testing
d----- 07/01/2020 12:22 PM quasar-app-extension-testing-unit-jest
Also, I can confirm that it's my environment that has an issue. I tried upgrading my colleagues copy to @quasar/app^1.4.3
and it works perfectly.
What else should I do? I've already done the following:
@quasar/cli
(both using yarn and npm)Try this sequence in the folder of the project:
npm -g cache clean --force
npm -g cache verify
npm cache clean --force
npm cache verify
yarn global remove @quasar/cli
npm -g uninstall @quasar/cli
npm -g install @quasar/cli
yarn remove @quasar/cli
npm uninstall @quasar/cli
// delete node_modules, yarn.lock, package-lock.json
yarn
quasar info
@pdanpdan I'll try this sequence. Will get back to you tomorrow for this. Thanks!
@pdanpdan Thanks! It's working now. Looks like my global cache was messed up.
Looking back, it might be due to running quasar upgrade
on two projects at the same time (where one or both fails).
@pdanpdan I had a similar issue with Quasar v2.7.0 and @quasar/app-weback v3.5.2 on a Win10 box. After running your list of command above, all worked properly. Thanks, Murray
"dev" command not found.
I simply forgot to run npm install
. Didn't expect to have this effect.
I was in the wrong folder when it happened to me. When I cloned the empty repo onto my computer, it created a folder and put the code inside there. Make sure you are in the right folder when running the command.
Try this sequence in the folder of the project:
npm -g cache clean --force npm -g cache verify npm cache clean --force npm cache verify yarn global remove @quasar/cli npm -g uninstall @quasar/cli npm -g install @quasar/cli yarn remove @quasar/cli npm uninstall @quasar/cli // delete node_modules, yarn.lock, package-lock.json yarn quasar info
hi, I have try this sequence, but still 'dev' is unknonw cmd, and my quasar info is : Operating System Windows_NT(10.0.22621) - win32/x64 NodeJs 16.14.0
Global packages NPM 8.3.1 yarn 1.22.22 @quasar/cli 2.4.0 @quasar/icongenie Not installed cordova Not installed
seems the existed project issue, I met the issue when I run under an existed project, it uses quasar v1.22.10 after checking package.json, then how can I try to install quasar/cli v1.22.10? I have tried "npm install -g @quasar/cli@1.22.10" but reports no match version found. and if I run under a new init project folder, it works well.
could you please help? thanks.
Describe the bug Upgrading to @quasar/app 1.4.3 makes the command
quasar dev
fail.Top error message after running the
quasar dev
command is:Tried to downgrade to
@quasar/app^1.4.2
and app runs properly.Codepen/jsFiddle/Codesandbox (required) I don't know how to set up this issue Codepen/jsFiddle/Codesandbox
To Reproduce Steps to reproduce the behavior:
@quasar/app^1.4.3
quasar dev
Expected behavior App should run in dev mode
Additional Info
What I've tried:
quasar -v
in my terminal and it shows1.0.5
while when I ran it in my colleague's terminal, it shows1.4.3
(after upgrade)Before Upgrade
After Upgrade to 1.4.3
quasar -version
Platform (please complete the following information): OS: Windows 10 Node: 12.14.0 NPM: 6.13.4 Yarn: 1.19.1 Terminal: Powershell Browsers: Chrome