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
Node 10.10 & 10.11 potential issues npm doesnt exist- node.exe vs node64.exe #398
Comments
Was this a new install? NVM4W rewrites node64.exe to node.exe for you, so this shouldn't be an issue. This can be solved with |
Yes, it was a new installs, come to think of it, i might have ran nvm install 10.10.0
nvm use 10.10.0 Which led to having node64.exe within the folder. |
It sounds like the environment may be a little unusual and is the most likely cause of the issue. However; I think this is a good edge case for illustrating the need for validation. I'm going to mark this as an enhancement request. Note to self: NVM4W should check for alternative architecture and at least warn the user if node.exe does not exist and either node32.exe or node64.exe exist. When possible, auto-correct. |
I have had the same problem on Win 7 Pro with nvm 1.1.6. nvm was reporting that cannot download npm. I found that the npm repository was moved. I have upgraded to nvm 1.1.7 and the problem was fixed. |
I wasn't able to download the npm neither because it was moved from https://github.com/npm/cli/archive/. |
Same here. |
same issue |
Fix is in version 1.1.7 https://github.com/coreybutler/nvm-windows/blob/1.1.7/src/nvm/web/web.go#L21 |
Ran into same issue on 1.1.7. Opted to hard link node.exe to node64.exe rather than edit the script. |
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
Not sure if this is a nvm or Node issue, I noticed this issue when downloading node 10.10.0 and node 10.11.0. did not have this issue with 10.9.0 or below.
but
npm.cmd
tries the call node.exe but the exe file name is node64.exe. So either had to rename the node exe file, or update thenpm.cmd
line.SET "NODE_EXE=%~dp0\node.exe"
to
SET "NODE_EXE=%~dp0\node64.exe"
just a heads up if anyone gets a cmd error of npm doesnt exist.
The text was updated successfully, but these errors were encountered: