Local build always gets stuck at npm ci

[lucadealfaro]

I have installed the correct versions of npm and node. When I do "npm ci --verbose", it invariably gets stuck with the last output being:

npm info run [email protected] install node_modules/zeromqold node-gyp-build
npm info run @playwright/[email protected] install { code: 0, signal: null }
npm info run [email protected] install { code: 0, signal: null }

I confirmed that I can install both [email protected] and .beta.6 in a separate environment.
In the pstree output, I see this:

       \-+= 20235 luca npm ci   
         |-+- 20292 luca node /Users/luca/Lavoro/work/vscode-jupyter-lda/node_modules/.bin/node-gyp-build
         | \--- 20360 luca /Users/luca/.nvm/versions/node/v22.15.1/bin/node
         |-+- 20313 luca node /Users/luca/Lavoro/work/vscode-jupyter-lda/node_modules/.bin/node-gyp-build
         | \--- 20358 luca /Users/luca/.nvm/versions/node/v22.15.1/bin/node
         \-+- 20356 luca node /Users/luca/Lavoro/work/vscode-jupyter-lda/node_modules/.bin/node-gyp-build
           \--- 20359 luca /Users/luca/.nvm/versions/node/v22.15.1/bin/node

All these processes have run for 0.07s max, and now are halted and don't do anything.
Does anyone have any hint on how to get unstuck?

[lucadealfaro]

If I interrupt (after hours) with ctrl-C, I get:

npm info run [email protected] install { code: null, signal: 'SIGINT' }
npm info run [email protected] install { code: null, signal: 'SIGINT' }
npm info run [email protected] install { code: null, signal: 'SIGINT' }
npm verbose stack Error: command failed
npm verbose stack     at promiseSpawn (/Users/luca/.nvm/versions/node/v22.15.1/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:22:22)
npm verbose stack     at spawnWithShell (/Users/luca/.nvm/versions/node/v22.15.1/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:124:10)
npm verbose stack     at promiseSpawn (/Users/luca/.nvm/versions/node/v22.15.1/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:12:12)
npm verbose stack     at runScriptPkg (/Users/luca/.nvm/versions/node/v22.15.1/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script-pkg.js:77:13)
npm verbose stack     at runScript (/Users/luca/.nvm/versions/node/v22.15.1/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script.js:9:12)
npm verbose stack     at /Users/luca/.nvm/versions/node/v22.15.1/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/rebuild.js:329:17
npm verbose stack     at run (/Users/luca/.nvm/versions/node/v22.15.1/lib/node_modules/npm/node_modules/promise-call-limit/dist/commonjs/index.js:67:22)
npm verbose stack     at /Users/luca/.nvm/versions/node/v22.15.1/lib/node_modules/npm/node_modules/promise-call-limit/dist/commonjs/index.js:84:9
npm verbose stack     at new Promise (<anonymous>)
npm verbose stack     at callLimit (/Users/luca/.nvm/versions/node/v22.15.1/lib/node_modules/npm/node_modules/promise-call-limit/dist/commonjs/index.js:35:69)
npm verbose pkgid [email protected]
npm error path /Users/luca/Lavoro/work/vscode-jupyter-lda/node_modules/utf-8-validate
npm error command failed
npm error signal SIGINT
npm error command sh -c node-gyp-build
npm verbose cwd /Users/luca/Lavoro/work/vscode-jupyter-lda
npm verbose os Darwin 24.6.0
npm verbose node v22.15.1
npm verbose npm  v10.9.2
npm verbose exit 1
npm verbose code 1
npm error A complete log of this run can be found in: /Users/luca/.npm/_logs/2025-12-12T21_12_32_053Z-debug-0.log