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
Alias for latest lts/non-lts/major #402
Comments
I believe that I have the same request/issue/feature... I would really like to use nvm in my nightly build process which would download and install the latest node version as well as USE IT so based on my manual process the first command: However, in order for an eventual automated script to use the latest version it would be really handy to be able to use the command: "nvm use latest" It currently appears that nvm simply adds .0.0 to the "latest" parameter and attempts to use an invalid version number of "latest.0.0"... Can the "nvm use" command be updated to allow for the keyword "latest" instead of a specific version number - to use the highest version currently available on the machine? |
nvm use $(nvm ls) works in powershell |
I have already created the following PRs:
However, they seem not to be merged. |
Maybe so, but it's important to keep the syntax identical to the original nvm, when working together in one project with folks on a Mac or Linux. That way, there can be no confusion as to what commands to use on nvm. |
My Environment
Windows 7 or below (not truly supported due to EOL - see wiki for details)
Windows 8
Windows 8.1
Windows 10
Windows 10 IoT Core
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016
My Windows installation is non-English.
I'm using NVM4W version:
I have already...
My issue is related to (check only those which apply):
Expected Behavior
I tried to install with
nvm install
,nvm install node
andnvm install latest
. I would expect one of these to install the latest version of Node.js. I would also expectnvm install 10
to install the latest 10.x.Fixing
nvm install node
would be in line with nvm even though it is a different thing - it is what mac/linux people use in place of nvm4w and having (mostly) identical commands will reduce confusion.Actual Behavior
When I run
nvm install node
, it says:When I run
nvm install 10
it installs 10.0.0, which might not what one woud expect.Steps to reproduce the problem:
Try the commands mentioned.
The text was updated successfully, but these errors were encountered: