Open JaKXz opened 5 years ago
Upon further reading... this is not really a great issue. It would be nice to have parity with nvm
- but that might be asking too much so feel free to close this issue. Thanks again!
I’d discourage you from using “stable” with nvm anyways, since everything is stable. Use node
or lts/*
to indicate which “latest” you want.
Agree with @ljharb, about using "stable", however nvs
could certainly give a better error message in that case.
Also I want to note that it is not a goal of nvs
to replicate all commands and behaviors of nvm
.
First of all, this is awesome, thank you for creating it! 🎉
nvm
has astable
keyword that points to the latest stable release of node (that's ahead of thelts/*
release). It would be great to have that innvs
so I don't have build failures like this: https://travis-ci.org/istanbuljs/nyc/builds/476649312?utm_medium=notification&utm_source=email