Skip to content
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

npm fallback #212

Closed
coreybutler opened this issue Oct 15, 2016 · 12 comments
Closed

npm fallback #212

coreybutler opened this issue Oct 15, 2016 · 12 comments

Comments

@coreybutler
Copy link
Owner

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.

@coreybutler
Copy link
Owner Author

Related to issue nodejs/nodejs.org#969

@sidneys
Copy link

sidneys commented Oct 18, 2016

Should be fixed now, as documented in:
nodejs/build#519

Imgur

@coreybutler
Copy link
Owner Author

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

@nbarnwell
Copy link

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.

@coreybutler
Copy link
Owner Author

@nbarnwell - cannot recreate.

image

@nZeus
Copy link

nZeus commented Aug 10, 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:
image

@nZeus
Copy link

nZeus commented Aug 10, 2018

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

@coreybutler
Copy link
Owner Author

coreybutler commented Aug 10, 2018

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

@javlc
Copy link

javlc commented Aug 10, 2018

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

@coreybutler
Copy link
Owner Author

@nagthgr8
Copy link

the issue still there with the latest 11.1.0

@coreybutler
Copy link
Owner Author

New repos and download URLs have been available for quite awhile and are integrated in newer versions of NVM4W. Closing (because I forgot to years ago).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants