-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
New node v8.4.0 and 8.5.0 installation broken npm #305
Comments
@coreybutler yes, it's a duplicate of #302, as I said. Just trying to fill more informations about my environment and the steps to replicate |
@Zorgatone - which is it?
The standard shell is not the same as cmder, even if you're running I did notice you're just trying to list the npm version, as opposed to installing semver. However; I still cannot recreate this in a standard terminal. I tried it in Cmder, and can't recreate it there either. I strongly suspect you're not getting a complete download of npm, which has semver as a dependency. Check the global |
@coreybutler checked also non-standard shell now, I forgot to click on the checkbox of both of them (I had tried on both terminals). Also I said I tried to add the missing dependencies (which means |
@Zorgatone - are you using a proxy or behind a firewall? The node executable is downloaded from the node releases on nodejs.org, but npm comes from https://github.com/npm/npm/archive by default, i.e. https://github.com/npm/npm/archive/v5.4.0.zip, which redirects to a different github URL (I believe https://codeload.github.com/npm/npm/zip/v5.4.0.zip?) If you're getting part of npm, but not the whole thing, the only thing I can think of is a network error. Proxies can cause this (i.e. not following a redirect, blocking domains, etc), and sometimes geographic location can cause this (network latency). Based on your profile, it looks like you're in Italy? It may be worth trying an npm mirror, though I'm not sure which is closest to you. |
Hello, any update on this? I am still experiencing similar issue - after installing node 8.5.0 the NPM is no longer accessible from a terminal - i guess the paths are busted. |
@coreybutler No, I wasn't using a proxy. I was using my home Wi-Fi connection (which is slow, but shouldn't lose packets that I know of, and I tried several times to download). I will try again this weekend to see if I can get it working on default Windows' CMD |
I have exactly the same problem that is described by zorgatone. node 6.x works but not 8.4 or newer. Same error "semver is missing..." |
I have the same problem too. |
Same problem on Windows Server 2012 R2. Tested with 8.5.0, 8.7.0, and 8.9.1. Had to install node manually from nodejs.org to resolve. |
@alesmenzel Unfortunately, no - I've been insanely busy lately. There's definitely an issue in npm and it's expected locations, so a workaround will be necessary. |
@coreybutler Thanks for response. I have managed to get it working with the latest node (8.9.1) and the 1.1.6 prerelease of nvm. There is small caveat though. I had to enable long paths in windows as npm was crashing on that. |
Closing issue as it is duplicate of #302 |
My Environment
Windows 7 or below (not truly supported due to EOL - see wiki for details)
Windows 8
Windows 8.1
Windows 10
Windows 10 IoT Core
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016
My Windows installation is non-English.
I'm using NVM4W version:
I have already...
My issue is related to (check only those which apply):
Expected Behavior
Install a working copy of latest Node JS and NPM
Actual Behavior
Installing seems to be completed and activated correctly. The Node interpreter seems to be the latest version and working. NPM seems to be the latest version but missing some node_modules dependencies. It won't load and even print
--help
or--version
Steps to reproduce the problem:
I opened my console (tried CMD not as admin (but admin user), open CMD with privileges, or even Powershell with or without privileges, disabled my AV - ESET Smart Security) and tried to install node 8.5.0 with the command
nvm install 8.5.0
and even with the commandnvm install latest 64 --insecure
.Both produce the same output and no errors on installation. Then I switch to the new version with
nvm use 8.5.0
and loads the new version correctly.node --version
andnode
seem to be working ok,nvm *anything*
won't work (missing packages in npm's node_modules dependencies, complaining aboutsemver
first, then I tried to add all of them and update npm withnpm install --global npm
but will say that it won't findnpm@undefined
even if I specify a version).Here's the output of my console (here using Cmder running cmd, on Windows 10 x64) when I try to get a new version of Node (I think 8.x won't work, as also noted for 8.4.0 here in issue #302, and here in version 8.5.0):
The text was updated successfully, but these errors were encountered: