nodejs_22: re-add patch to fix sandboxed builds using gyp on Darwin

[fugidev]

Fixes a regression introduced by #349157, which removed gypPatches for nodejs_22.

As was noted in the past, for some reason Node.js v22 vendors two different gyp versions:

• tools/gyp/
• deps/npm/node_modules/node-gyp/gyp/

v22.10.0 updated gyp in the former directory, making the patch in question obsolete. However, the latter vendored gyp still needs to be patched.

Apart from some flaky checks that seem unrelated to me, I've successfully tested building nodejs_22 and a yarn-berry package I'm working on, which failed before.

Maintainer ping: @aduh95

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/)
• Nixpkgs 25.11 Release Notes (or backporting 24.11 and 25.05 Nixpkgs Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
• NixOS 25.11 Release Notes (or backporting 24.11 and 25.05 NixOS Release notes)
  • (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, pkgs/README.md, maintainers/README.md and other contributing documentation in corresponding paths.

---

Add a 👍 reaction to pull requests you find important.

[aduh95]

nit: it might be better to refactor gyp-patches.nix to get the patch from there, but the current approach also LGTM.

I'm able to build this when rebased on top of staging-next.

[FliegendeWurst]

Suggested change

	url = "https://github.com/nodejs/gyp-next/commit/706d04aba5bd18f311dc56f84720e99f64c73466.patch";
	url = "https://github.com/nodejs/gyp-next/commit/706d04aba5bd18f311dc56f84720e99f64c73466.patch?full_index=1";

Or use the old fetchpatch. #257446

[aduh95]

FWIW it's unlikely to actually cause problems given the low activity on nodejs/gyp-next – but sure, let's fix it. gyp-patches.nix has the same issue btw:

nixpkgs/pkgs/development/web/nodejs/gyp-patches.nix

Line 4 in ce685a8

url = "https://github.com/nodejs/gyp-next/commit/706d04aba5bd18f311dc56f84720e99f64c73466.patch";

[FliegendeWurst]

I'll fix gyp-patches.nix.

FWIW it's unlikely to actually cause problems given the low activity on nodejs/gyp-next

It is possible to break the hash with some targeted commits in a fork, I think. (Though I really doubt anyone would try to ...)

[fugidev]

I committed the fix here

[nixpkgs-ci]

Successfully created backport PR for staging-25.05:

• [Backport staging-25.05] nodejs_22: re-add patch to fix sandboxed builds using gyp on Darwin #417453