On Mon, Jan 17, 2022 at 7:21 PM Stephen Gallagher <sgallagh(a)redhat.com> wrote:
Last week, I retired the `nodejs` package from EPEL 7 because it was
(I believed) stuck on Node.js 6.x due to insufficient dependency
support. Apparently, this broke a few things like uglify-js, so I
spent today looking into whether I could get Node.js 16.x to work (the
latest LTS release) and it turns out that I can indeed bludgeon it
into working. I have a COPR with a build of Node.js 16.x for EPEL 7
available to try while I await releng unretiring the package.
Please note: Node.js 16.x is a SIGNIFICANT version jump. It is very
probably that some of your Node packages may not work properly against
it. I urge anyone who is maintaining any such packages in EPEL 7 to
try them out against the aforementioned COPR prior to my building it
in EPEL proper.
This is now built and on its way to the epel-testing repository: