-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm install -g [email protected] with verbose loglevel crashes #3207
Comments
got this error on my local computer (osx) trying to update from 7.0.14 to 7.6.1 |
Same error for macOS 11.1, trying to update from 7.6.0 to 7.6.3. |
@sam-k @ChamNouki: If you're getting this error locally, it could be something with the local environment. When I encountered that in the past, I generally just installed the missing dependency and then upgraded just fine e.g.
The issue here is that these builds (via |
I'm on WSL2 Ubuntu 20.04 LTS Significantly, after installing node 15.11.0 with nvm, it installed npm v7.6.0, and the first use of npm showed:
Running that command failed with:
Eventually, running After upgrading without specifying a version, I can now specify a version and it works. Further information is that nvm is not the only way that node / npm were installed on the system. apt-get installed versions exist on the system too, possibly causing conflicts? |
On a non-M1 Macbook Pro, it fails as well. Tried;
|
Node.js 15.13.0 here with npm 7.8.0 Failing in my CI environment when trying to upgrade to 7.9.0:
Cross-posted from npm/cli#2818 |
Exact same thing here under Debian. But now, after the updates, I have two (2) items for each ... For each - Why would the original put |
I'm on an OSX 10.15.6 with Node 12.16.1 However - npm install -g npm did work without error - also as per @jeremydyoung above. |
I was having the same issue with
Here's the mentioned debug log: 2021-04-19T09_52_44_576Z-debug.log |
FYI - There is also an issue with Package.json variables, and the ability to override npm_package_ prefix variables. V7~ breaks the V6 behavior. See issue: [BUG] Package.json Vars $npm_config_{key} $npm_package_ are not in scope of the package.json scripts |
For those running WSL2: I had the same issue and tried |
Can confirm, just running |
I received this error on Ubuntu 20.04 (pure Ubuntu, not WSL). I got a notification to update to a new minor version:
When I ran the command, I received the same (click to expand)
|
Just had the exact same issue with 7.13.0. I installed the missing module with npm and then npm updated just fine. |
With |
UPDATE: Issue persists with
v15.11.0
and7.6.3
UPDATE 2: Issue resolved with
v16.3.0
and7.18.1
Environment
Expected Behavior
npm install -g [email protected]
should work.Current Behavior
Possible Solution
N/A
Steps to Reproduce
Create this
Dockerfile
in an empty folder. Runsudo docker build -t test:latest .
Filing bug here because this is the first time I have seen this issue in this environment.
I also can't seem to replicate running this locally (on my host machine).
The text was updated successfully, but these errors were encountered: