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

nvm install lts/current support? #3190

Closed
calidion opened this issue Sep 15, 2023 · 9 comments
Closed

nvm install lts/current support? #3190

calidion opened this issue Sep 15, 2023 · 9 comments

Comments

@calidion
Copy link

Operating system and version:

Any

Request

To support

nvm install lts

to install the latest lts version

nvm install current

to install the latest current version

@ljharb
Copy link
Member

ljharb commented Sep 15, 2023

Current isn't LTS. So, you just nvm install node.

@ljharb ljharb closed this as completed Sep 15, 2023
@calidion
Copy link
Author

current isn't lts.
so nvm install lts is needed.

@ljharb
Copy link
Member

ljharb commented Sep 15, 2023

nvm install lts/* or nvm install --lts already works, for LTS versions. But, the "Current" release line isn't and never will be LTS, so to install it you just install the latest version of node.

@calidion
Copy link
Author

nvm install lts/* or nvm install --lts already works, for LTS versions. But, the "Current" release line isn't and never will be LTS, so to install it you just install the latest version of node.

Thanks.

I mean use

nvm install current / lts

is more direct, intuitive, consistent with nodejs.

And I don't need to check the document to find it works for me.

@ljharb
Copy link
Member

ljharb commented Sep 15, 2023

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 :-)

@calidion
Copy link
Author

use

nvm install node

makes me think that we can potentially use

nvm install bun

And also I think using 'stable" is not proper because human beings make mistakes.
Release a stable version needs a lot of efforts.
Only a few releases can really be stable.
Such assumption tends to be wrong.
npm's range version and semver have such assumption and very big negative examples for such assumption.
That is why they turns out to be very problematic.

But current and lts have no such assumption, they are very objective deceptive nouns, will not bring such side effect.

@ljharb
Copy link
Member

ljharb commented Sep 16, 2023

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.

@calidion
Copy link
Author

Though the node project is a great project , the maintainers are not good at choosing right names and technical rules:)
I hope the bun support will be added soon:)

@ljharb
Copy link
Member

ljharb commented Sep 17, 2023

For that question, follow #3189.

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

No branches or pull requests

2 participants