chore: pass nodedir to node-gyp via npm_package_config env in node integration by reggi · Pull Request #9822 · npm/cli

reggi · 2026-07-30T16:04:53Z

What / Why

The node-integration workflow passed --nodedir as an npm CLI flag to npm install. In npm 12 unknown configs are no longer accepted, so this now fails with EUNKNOWNCONFIG:

npm error code EUNKNOWNCONFIG
npm error Unknown cli flag:
npm error - --nodedir

(seen in the Release Integration citgm jobs, e.g. citgm - bcrypt@6.0.0).

nodedir is a node-gyp option, not an npm config — it only ever worked via npm's old "accept arbitrary config and re-export as npm_config_*" behavior, which node-gyp itself notes was deprecated in npm v11 (nodejs/node-gyp#3156).

Change

Export npm_package_config_node_gyp_nodedir instead of using the CLI flag. This is node-gyp's preferred prefix since npm v11: node-gyp reads it directly from the environment, and npm does not warn on it — unlike npm_config_nodedir, which currently warns and is slated to error in npm 13.

This also matches how upstream nodejs/citgm supplies nodedir (via env, not a CLI flag).

Applied to both the generated .github/workflows/node-integration.yml and its scripts/template-oss/node-integration-yml.hbs template; template-oss-apply --lint passes.

…tegration The node integration workflow passed `--nodedir` as an npm CLI flag, which now errors with EUNKNOWNCONFIG in npm 12 since unknown configs are no longer accepted. `nodedir` is a node-gyp option, not an npm config. Switch to exporting `npm_package_config_node_gyp_nodedir`, node-gyp's preferred prefix since npm v11, which node-gyp reads directly and npm does not warn on (unlike `npm_config_nodedir`, which is slated to error in npm 13). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6e300b82-303b-49ac-ae93-52d984743d5b

github-actions · 2026-08-27T22:22:52Z

⚠️ Backport to release/v11 failed.

This usually means the cherry-pick had conflicts. Please create a manual backport:

git fetch origin release/v11
git checkout -b backport/v11/9822 origin/release/v11
git cherry-pick -x 278df04d3f25d391af3213a243bb9f89e1d11899
# resolve any conflicts, then:
git push origin backport/v11/9822

Error details

Command failed: git push origin backport/v11/9822
To https://github.com/npm/cli
! [remote rejected] backport/v11/9822 -> backport/v11/9822 (refusing to allow a GitHub App to create or update workflow `.github/workflows/node-integration.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/npm/cli'

…tegration (#9932) Backport of #9822 to `release/v11`. Copilot-Session: 744c3e7c-c466-43a7-b610-d67335f8dce3

reggi · 2026-07-30T16:04:53Z

What / Why

The node-integration workflow passed --nodedir as an npm CLI flag to npm install. In npm 12 unknown configs are no longer accepted, so this now fails with EUNKNOWNCONFIG:

npm error code EUNKNOWNCONFIG
npm error Unknown cli flag:
npm error - --nodedir

(seen in the Release Integration citgm jobs, e.g. citgm - bcrypt@6.0.0).

nodedir is a node-gyp option, not an npm config — it only ever worked via npm's old "accept arbitrary config and re-export as npm_config_*" behavior, which node-gyp itself notes was deprecated in npm v11 (nodejs/node-gyp#3156).

Change

Export npm_package_config_node_gyp_nodedir instead of using the CLI flag. This is node-gyp's preferred prefix since npm v11: node-gyp reads it directly from the environment, and npm does not warn on it — unlike npm_config_nodedir, which currently warns and is slated to error in npm 13.

This also matches how upstream nodejs/citgm supplies nodedir (via env, not a CLI flag).

Applied to both the generated .github/workflows/node-integration.yml and its scripts/template-oss/node-integration-yml.hbs template; template-oss-apply --lint passes.

…tegration The node integration workflow passed `--nodedir` as an npm CLI flag, which now errors with EUNKNOWNCONFIG in npm 12 since unknown configs are no longer accepted. `nodedir` is a node-gyp option, not an npm config. Switch to exporting `npm_package_config_node_gyp_nodedir`, node-gyp's preferred prefix since npm v11, which node-gyp reads directly and npm does not warn on (unlike `npm_config_nodedir`, which is slated to error in npm 13). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6e300b82-303b-49ac-ae93-52d984743d5b

github-actions · 2026-08-27T22:22:52Z

⚠️ Backport to release/v11 failed.

This usually means the cherry-pick had conflicts. Please create a manual backport:

git fetch origin release/v11
git checkout -b backport/v11/9822 origin/release/v11
git cherry-pick -x 278df04d3f25d391af3213a243bb9f89e1d11899
# resolve any conflicts, then:
git push origin backport/v11/9822

Error details

Command failed: git push origin backport/v11/9822
To https://github.com/npm/cli
! [remote rejected] backport/v11/9822 -> backport/v11/9822 (refusing to allow a GitHub App to create or update workflow `.github/workflows/node-integration.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/npm/cli'

…tegration (#9932) Backport of #9822 to `release/v11`. Copilot-Session: 744c3e7c-c466-43a7-b610-d67335f8dce3

reggi · 2026-07-30T16:04:53Z

What / Why

The node-integration workflow passed --nodedir as an npm CLI flag to npm install. In npm 12 unknown configs are no longer accepted, so this now fails with EUNKNOWNCONFIG:

npm error code EUNKNOWNCONFIG
npm error Unknown cli flag:
npm error - --nodedir

(seen in the Release Integration citgm jobs, e.g. citgm - bcrypt@6.0.0).

nodedir is a node-gyp option, not an npm config — it only ever worked via npm's old "accept arbitrary config and re-export as npm_config_*" behavior, which node-gyp itself notes was deprecated in npm v11 (nodejs/node-gyp#3156).

Change

Export npm_package_config_node_gyp_nodedir instead of using the CLI flag. This is node-gyp's preferred prefix since npm v11: node-gyp reads it directly from the environment, and npm does not warn on it — unlike npm_config_nodedir, which currently warns and is slated to error in npm 13.

This also matches how upstream nodejs/citgm supplies nodedir (via env, not a CLI flag).

Applied to both the generated .github/workflows/node-integration.yml and its scripts/template-oss/node-integration-yml.hbs template; template-oss-apply --lint passes.

…tegration The node integration workflow passed `--nodedir` as an npm CLI flag, which now errors with EUNKNOWNCONFIG in npm 12 since unknown configs are no longer accepted. `nodedir` is a node-gyp option, not an npm config. Switch to exporting `npm_package_config_node_gyp_nodedir`, node-gyp's preferred prefix since npm v11, which node-gyp reads directly and npm does not warn on (unlike `npm_config_nodedir`, which is slated to error in npm 13). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6e300b82-303b-49ac-ae93-52d984743d5b

github-actions · 2026-08-27T22:22:52Z

⚠️ Backport to release/v11 failed.

This usually means the cherry-pick had conflicts. Please create a manual backport:

git fetch origin release/v11
git checkout -b backport/v11/9822 origin/release/v11
git cherry-pick -x 278df04d3f25d391af3213a243bb9f89e1d11899
# resolve any conflicts, then:
git push origin backport/v11/9822

Error details

Command failed: git push origin backport/v11/9822
To https://github.com/npm/cli
! [remote rejected] backport/v11/9822 -> backport/v11/9822 (refusing to allow a GitHub App to create or update workflow `.github/workflows/node-integration.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/npm/cli'

…tegration (#9932) Backport of #9822 to `release/v11`. Copilot-Session: 744c3e7c-c466-43a7-b610-d67335f8dce3

reggi · 2026-07-30T16:04:53Z

What / Why

The node-integration workflow passed --nodedir as an npm CLI flag to npm install. In npm 12 unknown configs are no longer accepted, so this now fails with EUNKNOWNCONFIG:

npm error code EUNKNOWNCONFIG
npm error Unknown cli flag:
npm error - --nodedir

(seen in the Release Integration citgm jobs, e.g. citgm - bcrypt@6.0.0).

nodedir is a node-gyp option, not an npm config — it only ever worked via npm's old "accept arbitrary config and re-export as npm_config_*" behavior, which node-gyp itself notes was deprecated in npm v11 (nodejs/node-gyp#3156).

Change

Export npm_package_config_node_gyp_nodedir instead of using the CLI flag. This is node-gyp's preferred prefix since npm v11: node-gyp reads it directly from the environment, and npm does not warn on it — unlike npm_config_nodedir, which currently warns and is slated to error in npm 13.

This also matches how upstream nodejs/citgm supplies nodedir (via env, not a CLI flag).

Applied to both the generated .github/workflows/node-integration.yml and its scripts/template-oss/node-integration-yml.hbs template; template-oss-apply --lint passes.

…tegration The node integration workflow passed `--nodedir` as an npm CLI flag, which now errors with EUNKNOWNCONFIG in npm 12 since unknown configs are no longer accepted. `nodedir` is a node-gyp option, not an npm config. Switch to exporting `npm_package_config_node_gyp_nodedir`, node-gyp's preferred prefix since npm v11, which node-gyp reads directly and npm does not warn on (unlike `npm_config_nodedir`, which is slated to error in npm 13). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6e300b82-303b-49ac-ae93-52d984743d5b

github-actions · 2026-08-27T22:22:52Z

⚠️ Backport to release/v11 failed.

This usually means the cherry-pick had conflicts. Please create a manual backport:

git fetch origin release/v11
git checkout -b backport/v11/9822 origin/release/v11
git cherry-pick -x 278df04d3f25d391af3213a243bb9f89e1d11899
# resolve any conflicts, then:
git push origin backport/v11/9822

Error details

Command failed: git push origin backport/v11/9822
To https://github.com/npm/cli
! [remote rejected] backport/v11/9822 -> backport/v11/9822 (refusing to allow a GitHub App to create or update workflow `.github/workflows/node-integration.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/npm/cli'

…tegration (#9932) Backport of #9822 to `release/v11`. Copilot-Session: 744c3e7c-c466-43a7-b610-d67335f8dce3

reggi · 2026-07-30T16:04:53Z

What / Why

The node-integration workflow passed --nodedir as an npm CLI flag to npm install. In npm 12 unknown configs are no longer accepted, so this now fails with EUNKNOWNCONFIG:

npm error code EUNKNOWNCONFIG
npm error Unknown cli flag:
npm error - --nodedir

(seen in the Release Integration citgm jobs, e.g. citgm - bcrypt@6.0.0).

nodedir is a node-gyp option, not an npm config — it only ever worked via npm's old "accept arbitrary config and re-export as npm_config_*" behavior, which node-gyp itself notes was deprecated in npm v11 (nodejs/node-gyp#3156).

Change

Export npm_package_config_node_gyp_nodedir instead of using the CLI flag. This is node-gyp's preferred prefix since npm v11: node-gyp reads it directly from the environment, and npm does not warn on it — unlike npm_config_nodedir, which currently warns and is slated to error in npm 13.

This also matches how upstream nodejs/citgm supplies nodedir (via env, not a CLI flag).

Applied to both the generated .github/workflows/node-integration.yml and its scripts/template-oss/node-integration-yml.hbs template; template-oss-apply --lint passes.

…tegration The node integration workflow passed `--nodedir` as an npm CLI flag, which now errors with EUNKNOWNCONFIG in npm 12 since unknown configs are no longer accepted. `nodedir` is a node-gyp option, not an npm config. Switch to exporting `npm_package_config_node_gyp_nodedir`, node-gyp's preferred prefix since npm v11, which node-gyp reads directly and npm does not warn on (unlike `npm_config_nodedir`, which is slated to error in npm 13). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6e300b82-303b-49ac-ae93-52d984743d5b

github-actions · 2026-08-27T22:22:52Z

⚠️ Backport to release/v11 failed.

This usually means the cherry-pick had conflicts. Please create a manual backport:

git fetch origin release/v11
git checkout -b backport/v11/9822 origin/release/v11
git cherry-pick -x 278df04d3f25d391af3213a243bb9f89e1d11899
# resolve any conflicts, then:
git push origin backport/v11/9822

Error details

Command failed: git push origin backport/v11/9822
To https://github.com/npm/cli
! [remote rejected] backport/v11/9822 -> backport/v11/9822 (refusing to allow a GitHub App to create or update workflow `.github/workflows/node-integration.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/npm/cli'

…tegration (#9932) Backport of #9822 to `release/v11`. Copilot-Session: 744c3e7c-c466-43a7-b610-d67335f8dce3

reggi · 2026-07-30T16:04:53Z

What / Why

The node-integration workflow passed --nodedir as an npm CLI flag to npm install. In npm 12 unknown configs are no longer accepted, so this now fails with EUNKNOWNCONFIG:

npm error code EUNKNOWNCONFIG
npm error Unknown cli flag:
npm error - --nodedir

(seen in the Release Integration citgm jobs, e.g. citgm - bcrypt@6.0.0).

nodedir is a node-gyp option, not an npm config — it only ever worked via npm's old "accept arbitrary config and re-export as npm_config_*" behavior, which node-gyp itself notes was deprecated in npm v11 (nodejs/node-gyp#3156).

Change

Export npm_package_config_node_gyp_nodedir instead of using the CLI flag. This is node-gyp's preferred prefix since npm v11: node-gyp reads it directly from the environment, and npm does not warn on it — unlike npm_config_nodedir, which currently warns and is slated to error in npm 13.

This also matches how upstream nodejs/citgm supplies nodedir (via env, not a CLI flag).

Applied to both the generated .github/workflows/node-integration.yml and its scripts/template-oss/node-integration-yml.hbs template; template-oss-apply --lint passes.

…tegration The node integration workflow passed `--nodedir` as an npm CLI flag, which now errors with EUNKNOWNCONFIG in npm 12 since unknown configs are no longer accepted. `nodedir` is a node-gyp option, not an npm config. Switch to exporting `npm_package_config_node_gyp_nodedir`, node-gyp's preferred prefix since npm v11, which node-gyp reads directly and npm does not warn on (unlike `npm_config_nodedir`, which is slated to error in npm 13). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6e300b82-303b-49ac-ae93-52d984743d5b

github-actions · 2026-08-27T22:22:52Z

⚠️ Backport to release/v11 failed.

This usually means the cherry-pick had conflicts. Please create a manual backport:

git fetch origin release/v11
git checkout -b backport/v11/9822 origin/release/v11
git cherry-pick -x 278df04d3f25d391af3213a243bb9f89e1d11899
# resolve any conflicts, then:
git push origin backport/v11/9822

Error details

Command failed: git push origin backport/v11/9822
To https://github.com/npm/cli
! [remote rejected] backport/v11/9822 -> backport/v11/9822 (refusing to allow a GitHub App to create or update workflow `.github/workflows/node-integration.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/npm/cli'

…tegration (#9932) Backport of #9822 to `release/v11`. Copilot-Session: 744c3e7c-c466-43a7-b610-d67335f8dce3

reggi · 2026-07-30T16:04:53Z

What / Why

The node-integration workflow passed --nodedir as an npm CLI flag to npm install. In npm 12 unknown configs are no longer accepted, so this now fails with EUNKNOWNCONFIG:

npm error code EUNKNOWNCONFIG
npm error Unknown cli flag:
npm error - --nodedir

(seen in the Release Integration citgm jobs, e.g. citgm - bcrypt@6.0.0).

nodedir is a node-gyp option, not an npm config — it only ever worked via npm's old "accept arbitrary config and re-export as npm_config_*" behavior, which node-gyp itself notes was deprecated in npm v11 (nodejs/node-gyp#3156).

Change

Export npm_package_config_node_gyp_nodedir instead of using the CLI flag. This is node-gyp's preferred prefix since npm v11: node-gyp reads it directly from the environment, and npm does not warn on it — unlike npm_config_nodedir, which currently warns and is slated to error in npm 13.

This also matches how upstream nodejs/citgm supplies nodedir (via env, not a CLI flag).

Applied to both the generated .github/workflows/node-integration.yml and its scripts/template-oss/node-integration-yml.hbs template; template-oss-apply --lint passes.

…tegration The node integration workflow passed `--nodedir` as an npm CLI flag, which now errors with EUNKNOWNCONFIG in npm 12 since unknown configs are no longer accepted. `nodedir` is a node-gyp option, not an npm config. Switch to exporting `npm_package_config_node_gyp_nodedir`, node-gyp's preferred prefix since npm v11, which node-gyp reads directly and npm does not warn on (unlike `npm_config_nodedir`, which is slated to error in npm 13). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6e300b82-303b-49ac-ae93-52d984743d5b

github-actions · 2026-08-27T22:22:52Z

⚠️ Backport to release/v11 failed.

This usually means the cherry-pick had conflicts. Please create a manual backport:

git fetch origin release/v11
git checkout -b backport/v11/9822 origin/release/v11
git cherry-pick -x 278df04d3f25d391af3213a243bb9f89e1d11899
# resolve any conflicts, then:
git push origin backport/v11/9822

Error details

Command failed: git push origin backport/v11/9822
To https://github.com/npm/cli
! [remote rejected] backport/v11/9822 -> backport/v11/9822 (refusing to allow a GitHub App to create or update workflow `.github/workflows/node-integration.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/npm/cli'

…tegration (#9932) Backport of #9822 to `release/v11`. Copilot-Session: 744c3e7c-c466-43a7-b610-d67335f8dce3

reggi · 2026-07-30T16:04:53Z

What / Why

The node-integration workflow passed --nodedir as an npm CLI flag to npm install. In npm 12 unknown configs are no longer accepted, so this now fails with EUNKNOWNCONFIG:

npm error code EUNKNOWNCONFIG
npm error Unknown cli flag:
npm error - --nodedir

(seen in the Release Integration citgm jobs, e.g. citgm - bcrypt@6.0.0).

nodedir is a node-gyp option, not an npm config — it only ever worked via npm's old "accept arbitrary config and re-export as npm_config_*" behavior, which node-gyp itself notes was deprecated in npm v11 (nodejs/node-gyp#3156).

Change

Export npm_package_config_node_gyp_nodedir instead of using the CLI flag. This is node-gyp's preferred prefix since npm v11: node-gyp reads it directly from the environment, and npm does not warn on it — unlike npm_config_nodedir, which currently warns and is slated to error in npm 13.

This also matches how upstream nodejs/citgm supplies nodedir (via env, not a CLI flag).

Applied to both the generated .github/workflows/node-integration.yml and its scripts/template-oss/node-integration-yml.hbs template; template-oss-apply --lint passes.

…tegration The node integration workflow passed `--nodedir` as an npm CLI flag, which now errors with EUNKNOWNCONFIG in npm 12 since unknown configs are no longer accepted. `nodedir` is a node-gyp option, not an npm config. Switch to exporting `npm_package_config_node_gyp_nodedir`, node-gyp's preferred prefix since npm v11, which node-gyp reads directly and npm does not warn on (unlike `npm_config_nodedir`, which is slated to error in npm 13). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 6e300b82-303b-49ac-ae93-52d984743d5b

github-actions · 2026-08-27T22:22:52Z

⚠️ Backport to release/v11 failed.

This usually means the cherry-pick had conflicts. Please create a manual backport:

git fetch origin release/v11
git checkout -b backport/v11/9822 origin/release/v11
git cherry-pick -x 278df04d3f25d391af3213a243bb9f89e1d11899
# resolve any conflicts, then:
git push origin backport/v11/9822

Error details

Command failed: git push origin backport/v11/9822
To https://github.com/npm/cli
! [remote rejected] backport/v11/9822 -> backport/v11/9822 (refusing to allow a GitHub App to create or update workflow `.github/workflows/node-integration.yml` without `workflows` permission)
error: failed to push some refs to 'https://github.com/npm/cli'

…tegration (#9932) Backport of #9822 to `release/v11`. Copilot-Session: 744c3e7c-c466-43a7-b610-d67335f8dce3

reggi requested review from a team as code owners July 30, 2026 16:04

v-mragunandhan24 approved these changes Jul 30, 2026
View reviewed changes

martinrrm approved these changes Jul 30, 2026
View reviewed changes

reggi merged commit 278df04 into latestJul 30, 2026
26 checks passed

reggi deleted the reggi/node-integration-nodedir branch July 30, 2026 16:41

github-actionsBot mentioned this pull request Aug 3, 2026
chore: release 12.1.0 #9839
Open

reggi added the backport:v11 label Aug 27, 2026

reggi mentioned this pull request Aug 28, 2026
chore: pass nodedir to node-gyp via npm_package_config env in node integration #9932
Merged

reggi added a commit that referenced this pull request Aug 28, 2026
chore: pass nodedir to node-gyp via npm_package_config env in node in…
afdc5bd
…tegration (#9932) Backport of #9822 to `release/v11`. Copilot-Session: 744c3e7c-c466-43a7-b610-d67335f8dce3