An unofficial guide to which Node.js versions you should be using.
No.
It is not related to, or endorsed by, Node.js or the OpenJS Foundation.
The same place that the https://nodejs.org/en/about/previous-releases page gets it's information. There is a JSON file in the official Node.js Release Working Group repository, in the Node.js organization, on GitHub.
This website gets that file when you load the page, so it's always up to date.
On the https://nodejs.org/en/about/previous-releases page, they explain that library authors should use "Current" versions of Node.js to ensure that their library can support them. The page continues to say that "General use" and "Production apps" should use LTS versions.
When this website suggests that you should use specific version, it's purely based on those premises. This website makes no original suggestions about which version is best.
No.
I could have made one, but I don't want this website to be a key dependency in your CI/CD processes; and you shouldn't want it to be either! In my opinion you should always know what versions you're using in your pipelines and changing those versions should be a concious decision.
If you want ensure you're always up to date, I suggest setting a reminder in your calendar for the dates shown on this website. On the day of that reminder, come back here and see what the current recommendations are.
The same goes for if you happen to see a blog headline etc. declaring that a new version of Node.js has been released; come back here and see if you should be using it.
This website is unofficial. It is not related to, or endorsed by, Node.js or the OpenJS Foundation.
This website does not contain legal or security-related advice.
Made by Toby Smith with ❤ for Node.js and open-source!