nodejs: 16.15.0 -> 16.15.1, 18.2.0 -> 18.3.0

[marsam]

Description of changes

https://github.com/nodejs/node/releases/tag/v16.15.1

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
• 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/)
• 22.11 Release Notes (or backporting 22.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
  • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
• Fits CONTRIBUTING.md.

[etu]

Hey @nyanloutre @minijackson @purcell @jojosch

Somehow e6188b6 broke the build of jellyfin-web.

I'm not sure why, but I did bisect it to break in this commit. The same problem exists on hydra since 3 days ago: https://hydra.nixos.org/job/nixos/trunk-combined/nixpkgs.jellyfin-web.x86_64-linux

[yu-re-ka]

Hey @nyanloutre @minijackson @purcell @jojosch

Somehow e6188b6 broke the build of jellyfin-web.

I'm not sure why, but I did bisect it to break in this commit. The same problem exists on hydra since 3 days ago: https://hydra.nixos.org/job/nixos/trunk-combined/nixpkgs.jellyfin-web.x86_64-linux

#176127

[minijackson]

I'm not seeing any CVE fixed by the update to nodejs / npm, is it acceptable to revert this commit while waiting for a fix upstream?

[marsam]

is it acceptable to revert this commit while waiting for a fix upstream?

yes, reverted in #177002