$ the-wire · showcase
node-gyp 13.1.0 fixes --msvs_version, and citgm's red builds traced to loglevel precedence
By RepoJournal · Filed · About Node.js · Composed from the cited sources · methodology
node-gyp shipped 13.1.0 with a gyp-next bump and an argument-parsing fix, while the fix behind the citgm CI failures makes loglevel behave as documented again.
v13.1.0 nodejs/node-gyp
13.1.0 updates gyp-next to v0.22.3 and makes --msvs_version accept the spelling the README documents, so invocations copied from the docs stop failing on Visual Studio builds. Published 2026-10-02.
fix: let --loglevel on the command line override npm_config_loglevel nodejs/node-gyp
A fix lets --loglevel on the command line override npm_config_loglevel, restoring the precedence lost in v11.4.0; the description says it addresses the citgm node-gyp failure tracked in nodejs/citgm#1153, where three addon tests failed identically on every OS and Node.js 22, 24, and 26.
fix: let --loglevel on the command line override npm_config_loglevel (#3384) nodejs/node-gyp
The commit explains the regression plainly: since the npm_config_* handling landed in v11.4.0, environment variables were written into opts after argv was parsed, so an inherited npm_config_loglevel replaced an explicit --loglevel. It restores the old precedence for loglevel only; other options still read the environment last, and the options test now resets the shared logger instead of inherit...
chore(deps): bump undici nodejs/nodejs-dist-indexer
The dist indexer moves undici from 7.29.0 to 7.30.0, a bump that includes a backported fix to selectively re-enable SIMD for ppc64.
chore(deps): bump undici nodejs/changelog-maker
changelog-maker takes the same undici 7.29.0 to 7.30.0 bump, and both repos also picked up @semantic-release/github 12.0.9 to 12.0.10, with the accompanying 1.8.29 and 5.0.7 releases marking nothing more than dependency chores.
Action items
- → Upgrade node-gyp to 13.1.0 if you glob Visual Studio versions on the command line or under v11.4.0 nodejs/node-gyp [plan]
