On Mon, Jan 17, 2022 at 7:21 PM Stephen Gallagher <sgallagh@xxxxxxxxxx> 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[1], 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[2] with a build of Node.js 16.x for EPEL 7 > available to try while I await releng unretiring[3] 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. > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=2041022 > [2] https://copr.fedorainfracloud.org/coprs/sgallagh/nodejs_epel7/ > [3] https://pagure.io/releng/issue/10541 This is now built and on its way to the epel-testing repository: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-bf9c411793 _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
