-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Update NVM for Windows available from Chocolatey #757
Comments
I no longer have plans to maintain a chocolatey package for this project (that comment was from 7 years ago), so it would be better to bring this to the folks maintaining that effort. At this point, I'm taking a firm stance on not adding new features (like a new installation process), because they're distracting from the rt effort (the NVM4W successor). Just to be clear, I'm listening and recognize the desire for alternative installation methods (and other features). Feedback like is being taken into consideration for the next gen tool. |
Oh, that’s great. Thanks for all the work on NVM4W and I’m looking forward for rt! (And I’m sure @ljharb will appreciate the name change 😉.) |
Follow up for Chocolatey users out there: An update to NVM for Windows is on the way and you may get it now with: > choco install nvm --version=1.1.9 |
First of all, thanks for this project. It’s great! 😁
Second, I think this issue belongs here because you manifested interest in maintaining the Chocolatey package. Please let me know if I should bring this up with the Chocolatey people instead.
Issue:
The versions of NVM for Windows available from Chocolatey are old: https://community.chocolatey.org/packages/nvm (1.1.5) https://community.chocolatey.org/packages/nvm.portable (1.1.7)
These old versions don’t work anymore: npm/cli#4234
How To Reproduce:
Expected Behavior:
I think that the latest versions of NVM for Windows should be available from Chocolatey. After all, having an installer is great, but using a package manager is probably the most ergonomic way of install and manage development tools.
The text was updated successfully, but these errors were encountered: