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
Comments
Related to issue nodejs/nodejs.org#969 |
Should be fixed now, as documented in: |
@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.
If you go to https://github.com/npm/npm/releases/ there is no 6.2.0 available: |
Apparently |
@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? |
the issue still there with the latest 11.1.0 |
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). |
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.
The text was updated successfully, but these errors were encountered: