[staging-next-24.11] Node.js backports

[emilazy]

This brings the staging-next-24.11 Node.js derivation up to date with staging, apart from:

• the change to the default version;
• nodejs_22: use shared SQLite #352147 and the SQLite changes in e4f4440, since eating that rebuild right now seems awful;
• and 982e3fc since we don’t have the newer libuv on that branch.

I’m hoping this will fix #369690 (comment), but I still need to build it. It will be a fair few rebuilds to eat, of course; the alternative would be guessing at which parts of these make the difference and conditionalizing them on x86_64-darwin. Not sure that’s worth it.

I’m also not really sure what the cause of all this is; the only real changes to the Node derivation from release-24.11 to staging-next-24.11 are Python and libxml2 bumps, but the Python bump is on master as well. My hope is that it’s LLVM or something. My fear is that maybe we’re exposing some libuv issue that the bump on master hid. I dunno.

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.

[aduh95]

LGTM, although I suppose nodejs_22 will need the same libuv-related reverts as Node.js 23.x

[emilazy]

Ah, I foolishly only tested v20 to speed the process of unblocking staging-next-24.11 up. Will check the other versions too and patch as appropriate.

(We could potentially just upgrade libuv next cycle on 24.11, I don’t know if it’s breaking or not?)

[aduh95]

If that helps, I've opened #371201

(We could potentially just upgrade libuv next cycle on 24.11, I don’t know if it’s breaking or not?)

I didn't follow that closely but I don't think it created any breakage when it was updated on master/staging, so I'd expect it to not be too breaking – I tried to do that in #368368 but didn't find the time to investigate the ofborg failures

[emilazy]

Those just look like regular ofborg transient failures and timeouts rather than anything too concerning. Sorry for missing that PR; it should be fine to throw the SQLite changes and libuv bump in the next staging-24.11, if you wanted to rebase it.