-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
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 doesn't know the installed lts version is outdated. #3198
Comments
It's actually a very good thing it doesn't, because I agree that trying to install |
hmm, thinking about this more. if you wanted to stay on the LTS line, you'd have done I could certainly add some warning output when the version you may have expected to get has, due to server updates, changed - would that help? |
yeah, I think. Also this might be a bit more advanced, don't know if it's possible - it could check the LTS expiry date from a local lookup table. I think these dates are set in advance so it could cache a table from the last network call. |
I’m intentionally not going to make anything time-based in nvm; those dates change, and system clocks aren’t always correct, and EOL status doesn’t change what version of node you need. |
Right, I think in that case just a notice would work - using "latest locally installed lts version" or similar... |
For my usecase, I'd like to be able to ensure that my build is always installing the latest version from the |
@unlikelyzero no need; the install command will always get the latest version. The cache doesn’t prevent version listing, it only stores binaries and source. |
I typed
nvm use
while node 16 was installed as the lts version. It used 16 without actually checking whether it was the current LTS version. Would be good if it did the check.The text was updated successfully, but these errors were encountered: