Notify all open source projects on github to NOT use NodeJS 18 through a custom github bot and to remain on prior NodeJS releases (eg, 16.x) until absolutely necessary.Īpparently I didn't click "Commetn" on the last response that I wrote a few days ago so I'll re-draft it.
You can of course support it further than the LTS distros are supported (by purchasing or using the sponsored extended support). support the LTS versions for as long as the LTS version support exists. When this would actually be the best thing to do. Towards the end of Node.js 18's life cycle. We do not want to have to make a disruptive change
If we compare the linux support to window support, we can clearly see that linux is the least backwards supported platform requiring glibc 2.28 which released in August 1st 2018 (and wasn't included in distros until even later), while Windows has support for versions going back to 2015 for tier 1 support. Many developers use the official nodejs binaries in their projects One of the most important projects dependent on nodeJS 18 using bionic or an older distro is Electron This of course will trickle down to 1000s of dependent projects. The breaking change that has been implemented will cause many projects dependent on NodeJS to drop centos 7, rhel 7, and (more importantly) Ubuntu bionic and Ubuntu 18 (bionic in snaps). All of them have support well past the EOL of NodeJS 18 when paired with paid or free (through sponsorship) extended support. Nodejs/build#2741 What is the feature you are proposing to solve the problem?īuilding on one of these older distros. Linux distributions with a matching or higher version of glibc.
The official Node.js Linux release binaries will only run on Moving to RHEL 8 has raised the glibc version being linked against What is the problem this feature will solve?
0 kommentar(er)
