Nvm-windows: npm fallback

Created on 15 Oct 2016 · 11Comments · Source: coreybutler/nvm-windows

The node.js JSON feed sometimes has bad data (see issue #211). NVM4W should provide a fallback to download the latest available version of npm if no other version is specified.

edge case help wanted

Source

coreybutler

Most helpful comment

@nZeus - Check your version of nvm. The npm repo changed, and NVM4W v1.1.7 uses the new URL.

coreybutler on 10 Aug 2018

👍3

All 11 comments

coreybutler on 15 Oct 2016

Should be fixed now, as documented in:
https://github.com/nodejs/build/issues/519

Imgur

sidneys on 18 Oct 2016

@sidneys - thanks for the update, and I'm glad to see it working.

I'm still going to leave this issue open because I think NVM4W needs to handle this scenario in case it happens again.

coreybutler on 19 Oct 2016

Yeah so this is happening again with node 10.8.0. I'm going to have to ditch nvm and install node the old-fashioned way, since it doesn't look like this workaround is going to be implemented. Probably best to just close this issue if not.

nbarnwell on 9 Aug 2018

👍1

@nbarnwell - cannot recreate.

coreybutler on 10 Aug 2018

Cannot install 10.8.0.

Downloading npm version 6.2.0... Download failed. Rolling Back.                                                                                                      
Rollback failed. remove C:\Users\i.tsvetkov\AppData\Roaming\nvm\temp\npm-v6.2.0.zip: The process cannot access the file because it is being used by another process. 
Could not download npm for node v10.8.0.                                                                                                                             
Please visit https://github.com/npm/npm/releases/tag/v6.2.0 to download npm.                                                                                         
It should be extracted to C:\Users\i.tsvetkov\AppData\Roaming\nvm\v10.8.0

If you go to https://github.com/npm/npm/releases/ there is no 6.2.0 available: