-
-
Notifications
You must be signed in to change notification settings - Fork 746
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
[feature request] add the previous version in the output. #825
Comments
I am not sure what this means. But I understand I'll clarify what you see when you install. When the target version is not already in the cache, like when a new version comes out, it is downloaded into the cache and installed (copied) into $ n latest
installing : node-v23.4.0
mkdir : /usr/local/n/versions/node/23.4.0
fetch : https://nodejs.org/dist/v23.4.0/node-v23.4.0-darwin-arm64.tar.xz
copying : node/23.4.0
installed : v23.4.0 (with npm 10.9.2) When the target version is already in the cache, it is copied into $ n ls
node/18.20.4
node/20.18.0
node/22.12.0
node/23.4.0
$ n latest
copying : node/23.4.0
installed : v23.4.0 (with npm 10.9.2) We can also see/do the download and install separately for a new version: $ n rm latest
latest (23.4.0) not in downloads cache
$ n download latest
download : node-v23.4.0
mkdir : /usr/local/n/versions/node/23.4.0
fetch : https://nodejs.org/dist/v23.4.0/node-v23.4.0-darwin-arm64.tar.xz
$ n install latest
copying : node/23.4.0
installed : v23.4.0 (with npm 10.9.2) |
Thanks for the details. That's really just like adding |
surprisingly even |
I like to run
sudo n latest
every now and then to make sure I'm always on the last version of NodeJS. The problem withn
is that it's not always apparent whether node got updated or not. And if it does it doesn't necessarily show what upgrade it got.In the output it would be nice to also show the previous version, e.g.
The text was updated successfully, but these errors were encountered: