You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nvm install is for installing node versions. To install nvm itself, you need to use nvm's install command, listed in its readme: https://github.com/nvm-sh/nvm
@ljharb@Heitor-hub-del Frankly, it's hard for us to keep updating nvm every time a patch version is released. Would one the following solutions be possible
Use the HEAD tag.
Have nvm PR here when they want the website to change?
certainly don't offer a way to naively and blindly update to the latest version, and if they do, that's a horrific practice that node shouldn't be endorsing.
We're not even arguing about this (updating nvm automatically), but fresh installs having a permanent link that redirects to the latest version of your install script. If you had a get.nvm.sh that is just a 301 to whatever the latest version is, that'd be great.
Also, I think it is unfair saying Im being hostile. I am just giving my opinions on the matter, which differs from yours. And we just won't do what you want us to do. That isn't being hostile.
If you had a get.nvm.sh that is just a 301 to whatever the latest version is, that'd be great.
Or just a tag on the repo that matches the latest release
All these alternatives work, but require Jordan to change his stance, which I don't want to force him to. I sent a DM to @ljharb and quoting, I'm OK if the alternative is we (the Node.js website) add a GHA workflow (cron) that periodically patches the nvm MD files with the latest version. Am I happy with that? Not really. Do I think it is ideal? Absolutely not. But it is a solution to our users. I don't want us to be in a stalemate, I want to solve for our users and community. (regardless of what my opinions are -- in this specific matter)
Frankly, it's hard for us to keep updating nvm every time a patch version is released.
Hard? no. This was the first release in 10 months.
I am not really a believer that everything be some automated solution. This is low-barrier, quick to verify contribution.
I think we could have avoided a lot of stress in this thread by labeling the issue good first issue and encouraging the community to contribute it.
Frankly, it's hard for us to keep updating nvm every time a patch version is released.
Hard? no. This was the first release in 10 months. I am not really a believer that everything be some automated solution. This is low-barrier, quick to verify contribution.
I think we could have avoided a lot of stress in this thread by labeling the issue good first issue and encouraging the community to contribute it.
That is a completely fair route. I think the gist of this discussion is: Are we fine with the status quo? And if not, what are the alternatives? I'm fine keeping as is too, tbh.
Activity
Heitor-hub-del commentedon Feb 14, 2026
basically a simple feature request, i know that it doesnt switch a version to another one but.... its always good to be up to date :)
Renegade334 commentedon Feb 14, 2026
Node.js does not bundle nvm. If you have it installed, then updating it is your responsibility.
ljharb commentedon Feb 14, 2026
I think this is for the website.
Heitor-hub-del commentedon Feb 14, 2026
Heitor-hub-del commentedon Feb 14, 2026
wdym it "doesnt bundle"
ljharb commentedon Feb 14, 2026
nvm installis for installing node versions. To install nvm itself, you need to use nvm's install command, listed in its readme: https://github.com/nvm-sh/nvmavivkeller commentedon Feb 14, 2026
@ljharb @Heitor-hub-del Frankly, it's hard for us to keep updating nvm every time a patch version is released. Would one the following solutions be possible
HEADtag.fyi @nodejs/nodejs-website
6 remaining items
ovflowd commentedon Feb 15, 2026
We're not even arguing about this (updating nvm automatically), but fresh installs having a permanent link that redirects to the latest version of your install script. If you had a get.nvm.sh that is just a 301 to whatever the latest version is, that'd be great.
ovflowd commentedon Feb 15, 2026
Also, I think it is unfair saying Im being hostile. I am just giving my opinions on the matter, which differs from yours. And we just won't do what you want us to do. That isn't being hostile.
avivkeller commentedon Feb 15, 2026
Or just a tag on the repo that matches the latest release
ovflowd commentedon Feb 15, 2026
All these alternatives work, but require Jordan to change his stance, which I don't want to force him to. I sent a DM to @ljharb and quoting, I'm OK if the alternative is we (the Node.js website) add a GHA workflow (cron) that periodically patches the nvm MD files with the latest version. Am I happy with that? Not really. Do I think it is ideal? Absolutely not. But it is a solution to our users. I don't want us to be in a stalemate, I want to solve for our users and community. (regardless of what my opinions are -- in this specific matter)
bmuenzenmeyer commentedon Feb 15, 2026
Hard? no. This was the first release in 10 months.
I am not really a believer that everything be some automated solution. This is low-barrier, quick to verify contribution.
I think we could have avoided a lot of stress in this thread by labeling the issue
good first issueand encouraging the community to contribute it.ovflowd commentedon Feb 15, 2026
That is a completely fair route. I think the gist of this discussion is: Are we fine with the status quo? And if not, what are the alternatives? I'm fine keeping as is too, tbh.
rishabhdo1 commentedon Feb 19, 2026
Hi! I'm a beginner open source contributor and I'd love to
work on this. Could you please assign it to me? I'll submit
a PR shortly.
avivkeller commentedon Feb 19, 2026
We don’t assign issues, but you are welcome to submit a PR
[actions] add workflow to update nodejs.org nvm version
[actions] add workflow to update nodejs.org nvm version
[actions] add workflow to update nodejs.org nvm version
[actions] add workflow to update nodejs.org nvm version