Nvm-windows: npm fallback

Related to issue https://github.com/nodejs/nodejs.org/issues/969

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

Imgur

@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.

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 - cannot recreate.

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:

Apparently nvm is trying to reach the wrong repo. It should use https://github.com/npm/cli/releases

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

Is there a command to upgrade nvm v1.17, or just re run the new installer?

@javlc https://github.com/coreybutler/nvm-windows#installation--upgrades

the issue still there with the latest 11.1.0