#2391 F33 System-Wide Change: Node.js 14.x by default
Opened 23 days ago by bcotton. Modified 2 days ago

The latest release of Node.js to carry a 30-month lifecycle is the 14.x series. As with 12.x, 10.x and 8.x before it, Fedora 33 will carry 14.x as the default Node.js interpreter for the system. The 12.x interpreter will remain available as a non-default module stream.


This will either be the nodejs:14 module stream or else replicated to the non-modular repository, depending on the status of other release engineering work around supporting modular content in the non-modular buildroots.

I am not sure if this should be in the description, but probably something what should be put in release notes if that happens (default modular stream).

For those whose applications do not yet work with the 14.x release, Fedora 33 will also have the 12.x release available as a selectable module stream.

Hmm, do you have such list of packages? Or you mean some hypothetical applications which users install from somewhere not as RPM? If former, who is going to do the conversion to a modules and such?

Any developer with a package that depends on Node.js at run-time or build-time should test with the 14.x module stream enabled as soon as possible.

Not really a blocker or anything, but would it be possible to provide the build in a side tag and perform rebuild of affected packages in there to see the impact?
Just trying to say that I am happy that we are moving forward, but it would be useful to know how much stuff breaks in advance and prepare such upgrades better.

Release engineering and FESCo will need to approve the change to the default module stream.

Hmm, so is that thing which is supposed to happen or not? So far we have them blocked, so is this proposal essentially mean that we will allow default modular stream for nodejs?

There were some clarifications on the devel thread, I like to see the proposal updated. Procedural -1 until that happens (I am prepared to vote in favor when that happens).

Technically, that -1 means we should discuss this in the meeting, but as I am the one responsible for updating the Change Proposal and haven't yet, I'm going to defer it.

We're still waiting for the update from @sgallagh here.

Metadata Update from @zbyszek:
- Issue assigned to sgallagh

10 days ago

Still waiting for an update.

Apologies for the delay. I believe this is now updated with all of the comments from the fedora-devel thread.

This will either be the nodejs:14 module stream or else replicated to the non-modular repository, depending on the status of other release engineering work around supporting modular content in the non-modular buildroots.

This has not been updated. The contingency plan also only talks about default streams.

Sorry, I missed some sections. Fixed now.

+1, though the docs should be updated a bit more imo:

Fedora 33 will ship with the latest LTS version of Node.js in the non-modular repository.
To end-users, the experience should be identical: dnf install nodejs will give them nodejs-14.x and the matching npm package.

I know where you're coming from, but that's just confusing without knowing the history of this ticket. Maybe something like this:

Fedora 33 will ship with the latest LTS version of Node.js. dnf install nodejs will give users nodejs-14.x and the matching npm package.

(The discussion of modules in Scope section is OK.)

Any developer with a package that depends on Node.js at run-time or build-time should test with the 14.x module stream enabled as soon as possible.

Is there a way to e.g. do that in mock and/or koji --scratch?

Login to comment on this ticket.

Metadata