nodejs_latest: 23.11.0 -> 24.0.0-rc.2

[aduh95]

Opening things now so it can land before the 25.05 freeze. This removes nodejs_23 (which is now in Maintenance mode, and will be EOL in June, i.e. during 25.05 lifetime) and initiates nodejs_24 (still RC state, 24.0.0 is scheduled for April 22nd).

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[happysalada]

The diff looks good, do you have a link to the changelog ? Im on mobile and i wasnt young enough to figure out how to get it from the github app.
The idea would be just to have a sense of what will break and what we should look out for.

[aduh95]

There's no changelog per se for the RC versions, there's a WIP one for 24.0.0 in nodejs/node#57609

[winterqt]

I'd be fine with landing this with the proper release tag on the 22nd, if they keep their timeline.

[aduh95]

@winterqt can you clarify what you'd like to see on 25.05 wrt nodejs_latest and nodejs_23 if this PR is not ready in time for the cutoff? I understand you present the best case scenario, but given how tight the timeline is, we should discuss what we want to happen if we leave the happy path (FWIW I think it'd be wiser not to wait and land this as is, it's easy enough to PR the nodejs_24 version bump once the actual 24.0.0 is released, and since this is targeting staging, it should be plenty of time to make the update before even unstable is affected)

[happysalada]

@winterqt what do you think about the proposal to merge this as is and backport the update from rc to stable ?
Since 23 is going to be end of life it makes sense to me.

[happysalada]

@winterqt im sure you know but antoine here is one of the nodejs contributors, it would be nice to give him an answer so we can keep a good relationship with upstream maintainers.

[winterqt]

Let's give it a shot.

(Sorry for the delay.)

[happysalada]

Thank you !