Open PyroSA opened 9 years ago
Just encountered this problem myself. I installed nvm-windows manually, and it appears that the application doesn't correctly update the %NVM_SYMLINK%
property, since as the session value never changes after using the nvm use <version>
command.
C:\Users\<USERNAME>
λ echo %NVM_SYMLINK%
C:\ << session variable is 'C:\'
C:\Users\<USERNAME>
λ nvm list
5.4.0
4.2.4
0.12.1
0.11.12
C:\Users\<USERNAME>
λ nvm use 5.4.0
Now using node v5.4.0 (64-bit)
C:\Users\<USERNAME>
λ nvm list
5.4.0 << version I selected isn't enabled
4.2.4
0.12.1
0.11.12
C:\Users\<USERNAME>
λ echo %NVM_SYMLINK%
C:\ << session variable hasn't updated
C:\Users\<USERNAME>
λ set NVM_SYMLINK="C:\WAFFES"
C:\Users\<USERNAME>
λ echo %NVM_SYMLINK%
"C:\WAFFES" << session variable updated by me
λ nvm install v6.10.0 Downloading node.js version 6.10.0 (64-bit)... Complete Creating C:\Users\hackj\AppData\Roaming\nvm\temp
Downloading npm version 3.10.10... Error while downloading https://github.com/npm/npm/archive/v3.10.10.zip - unexpected EOF Complete Installing npm v3.10.10...
Installation complete. If you want to use this version, type
npm doesn't included and cannot work !
Same issue as @hackjus
What I did:
What I expected:
What I get: C:\Users\Vincent>nvm install 10.16.0 Downloading node.js version 10.16.0 (64-bit)... Complete Creating C:\development\web\nvm\temp
Downloading npm version 6.9.0... Error while downloading https://github.com/npm/cli/archive/v6.9.0.zip - unexpected EOF Complete Installing npm v6.9.0...2020/02/06 10:38:15 Failed to extract npm. Could not find C:\development\web\nvm\temp\nvm-npm\npm-6.9.0\bin
C:\Users\Vincent>nvm use 10.16.0 Now using node v10.16.0 (64-bit)
C:\Users\Vincent>node --version v10.16.0
C:\Users\Vincent>npm 'npm' is not recognized as an internal or external command, operable program or batch file.
### UPDATE Feb/02/2020 I deleted all old files and reinstalled it through the installer. All things somehow works, I was quite confused about the abnormality. I will try to figure it out and hope others who encounter the same issue could find the reason as well.
### UPDATE Feb/02/2020 I deleted all old files and reinstalled it through the installer. All things somehow works, I was quite confused about the abnormality. I will try to figure it out and hope others who encounter the same issue could find the reason as well.
This is really strange. I do hope this bug is fixed.
NVM install errors (connection fails), but NVM completes as if nothing went wrong.
If this error occurs during NPM install, it seems to report the node version as already installed, but npm gives an error as per #62