2 ms·
The biggest impact of this change is for organizations with big codebases who want to stay on LTS versions. With the canonical schedule you can do an upgrade e
by nilsbunger 4y ago
The biggest impact of this change is for organizations with big codebases who want to stay on LTS versions.
With the canonical schedule you can do an upgrade every 2 years, skipping over every other LTS. eg you could go from Node 14 to Node 18 to Node 22.
But with the early EOL, if you're on Node 16 you can't jump to Node 20, so you have to do an extra upgrade.
For companies with big production codebases it can be a lot of work to qualify new releases.
It would be great if the Node team pulls forward Node 20 LTS by 6 months to preserve the skip-every-other pattern.
https://nodejs.org/en/about/releases/ https://nodejs.org/en/about/releases/