npm / node-gyp
node-gyp
What changed in node-gyp 4 to 13, from its official release notes, upgrade guides and advisories. Sources checked 2026-11-01.
5 breaking3 behavior and defaults7 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli initnode-gyp 134 changes
Fixes and other changes 4
The command-line option now overrides npm_config_loglevel.
Accepts --msvs_version as documented.
Falls back gracefully when build symlink creation fails.
Fixes the Windows VS2026 version handling.
node-gyp 111 changes
Breaking changes 1
Node.js 16 is no longer supported.
node-gyp 106 changes
Breaking changes 3
Internal functions now return promises and no longer accept callbacks, which may affect consumers that require them directly.
The supported Node.js versions are now ^16.14.0 or >=18.0.0; Node.js 14 is no longer supported.
The order of Python checks on Windows has changed, which may affect which Python installation node-gyp finds.
Behavior and default changes 3
The exported Gyp class is now created using ECMAScript classes, which may cause small differences from classes created with util.inherits.
Published files are now limited using .npmignore, which changes which files are included in the package.
The Python symlink is created only during builds and cleaned up afterward.
node-gyp 93 changes
Breaking changes 1
The supported Node.js versions are now ^12.22, ^14.13, or >=16.
Fixes and other changes 2
On z/OS, lib.target is now searched as a path for libnode.
Underscores in npm_config_ environment variables are handled.
node-gyp 41 changes
Fixes and other changes 1
Uses print() when detecting the Python version.