-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
nvm install lts/current
support?
#3190
Comments
Current isn't LTS. So, you just |
current isn't lts. |
|
Thanks. I mean use
is more direct, intuitive, consistent with nodejs. And I don't need to check the document to find it works for me. |
Ah, you mean you want a “current” alias built-in that means the same as “node”. ‘We’re already stuck with “stable” from pre-io.js days, and i wouldn’t want to be stuck with “current” one day too :-) |
use
makes me think that we can potentially use
And also I think using 'stable" is not proper because human beings make mistakes. But |
That’s the right understanding, because you can also use nvm install iojs. In the v0.x days, node had “stable” and “unstable” releases, and that’s what that referred to. All of these names have been official choices of the node project. |
Though the node project is a great project , the maintainers are not good at choosing right names and technical rules:) |
For that question, follow #3189. |
Operating system and version:
Any
Request
To support
to install the latest lts version
to install the latest current version
The text was updated successfully, but these errors were encountered: