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

Alias latest to stable #2103

Open
dominykas opened this issue Sep 23, 2019 · 1 comment
Open

Alias latest to stable #2103

dominykas opened this issue Sep 23, 2019 · 1 comment

Comments

@dominykas
Copy link

dominykas commented Sep 23, 2019

There was a similar issue #731 way back when, and it was closed for a reason, however I think it might be worth revisiting.

As part of scanning top 1000 packages in the ecosystem for .travis.yml, I found that 3 (yes, that's 0.3%) use latest as one of the options in the list of the versions they want to test. Naturally, they have failing builds.

I suspect there might be more people using this keyword, so it might be useful to just help them out and make latest install stable (aka node).

@ljharb
Copy link
Member

ljharb commented Sep 23, 2019

It's not a bad suggestion.

At this point, though, unless I was able to add a way to suppress most "default"/"built in" aliases when not locally installed, but leave them discoverable, I'm hesitant to add more of them. nvm ls output is noisy enough.

For example, if unstable and stable could always be hidden, but functional, and iojs could be hidden when no io.js version was installed - but the nvm alias output hinted at some kind of nvm alias --all/nvm ls --all-aliases command that listed them all - then i'd probably want to add latest, and make node no longer be the encouraged form, since i think "latest" is a bit clearer.

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