Dear Maintainer,
This is similar to #1133310, but I am running into the bug when running `# npm install -g <package>`. Similar to that bug, there is absolutely no clue in the logfile --- it simply prints the version of node and npm and then immediately exits:
# npm --ddd install -g @peertube/peertube-runner
npm verbose cli /usr/bin/node /usr/bin/npm
npm info using npm@11.12.1
npm info using node@v22.22.2
npm silly config load:file:/usr/share/nodejs/npm/npmrc
npm silly config load:file:/root/.npmrc
npm silly config load:file:/etc/npmrc
npm verbose title npm install @peertube/peertube-runner
npm verbose argv "--loglevel" "silly" "install" "--global" "@peertube/peertube-runner"
npm verbose logfile logs-max:10 dir:/root/.npm/_logs/2026-04-23T00_09_17_295Z-
npm verbose logfile /root/.npm/_logs/2026-04-23T00_09_17_295Z-debug-0.log
npm silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
npm silly logfile start cleaning logs, removing 1 files
npm silly logfile done cleaning log files
npm silly idealTree buildDeps
npm silly fetch manifest @peertube/peertube-runner@*
npm silly packumentCache full:https://registry.npmjs.org/@peertube%2fpeertube-runner cache-miss
npm http cache https://registry.npmjs.org/@peertube%2fpeertube-runner 10ms (cache hit)
npm silly packumentCache full:https://registry.npmjs.org/@peertube%2fpeertube-runner set size:45791 disposed:false
npm silly placeDep ROOT @peertube/peertube-runner@0.5.1 OK for: want: *
npm silly reify mark retired [ '/usr/local/lib/node_modules/@peertube/peertube-runner' ]
npm silly reify moves {
npm silly reify '/usr/local/lib/node_modules/@peertube/peertube-runner': '/usr/local/lib/node_modules/@peertube/.peertube-runner-RmkeMd1R'
npm silly reify }
npm http cache @peertube/peertube-runner@https://registry.npmjs.org/@peertube/peertube-runner/-/peertube-runner-0.5.1.tgz 0ms (cache hit)
npm verbose cwd /home/chiraag
npm verbose os Linux 6.19.11+deb14-amd64
npm verbose node v22.22.2
npm verbose npm v11.12.1
npm verbose exit 1
npm verbose code 1
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-04-23T00_09_17_295Z-debug-0.log
I can confirm this has happened for a long time, many months ago since last year. npm is no longer usable for me on Debian until this is fixed.
- -- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 7.1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages npm depends on:
ii ca-certificates 20260601
ii node-abbrev 1.1.1+~1.1.2-1
ii node-agent-base 7.1.4~0~2025070717+~cs15.3.8-1
ii node-anymatch [node-picomatch] 3.1.3+~cs8.0.6-1
ii node-aproba 2.1.0-1
ii node-archy 1.0.0-8
ii node-base64-js 1.5.1+dfsg+~1.3.0-3
ii node-binary-extensions 2.2.0-2
ii node-buffer 6.0.3-3
ii node-cacache 20.0.4+~cs30.1.8-2
ii node-chalk 5.6.2+dfsg-5
ii node-chownr 3.0.0-2
ii node-ci-info 4.4.0+~cs8.2.0-3
ii node-cli-table [node-cli-table3] 0.3.11+~cs0.13.4-3
ii node-cliui [node-jackspeak] 7.0.4+repack+1+~cs1.4.2-2
ii node-columnify 1.6.0+~1.5.4-1
ii node-css-loader [node-postcss-selector-pars 6.8.1+~cs14.0.17-2
er]
ii node-css-selector-tokenizer [node-cssesc] 0.8.0+~cs4.8.3-1
ii node-debug 4.4.3+~4.1.13-1
ii node-deep-equal [node-hasown] 2.2.3+ds1+~cs43.15.94-1
ii node-diff 8.0.3~dfsg-2
ii node-encoding 0.1.13-2
ii node-env-paths 3.0.0-3
ii node-events 3.3.0+~3.0.3-1
ii node-foreground-child 4.0.3-1
ii node-glob 13.0.6+~cs0.4.15-1
ii node-got 11.8.5+~cs58.13.36-6
ii node-graceful-fs 4.2.11-1
ii node-gyp 12.3.0+~6.1.0-1
ii node-hosted-git-info 9.0.2-1
ii node-http-proxy-agent 7.0.2~0~2025070717+~cs15.3.8-1
ii node-https-proxy-agent 7.0.6~0~2025070717+~cs15.3.8-1
ii node-ieee754 1.2.1-3
ii node-ini 3.0.1-2
ii node-ip-regex 4.3.0+~4.1.1-1
ii node-json-parse-better-errors 1.0.2+~cs3.3.1-3
ii node-jsonparse 1.3.1-10
ii node-lru-cache 11.2.7-6
ii node-minimatch 9.0.7-1
ii node-minipass 7.1.3+~cs21.1.8-3
ii node-mkdirp 3.0.1+~cs5.2.1-2
ii node-ms 2.1.3+~cs0.7.31-3
ii node-negotiator 0.6.3+~0.6.1-1
ii node-nopt 9.0.0-1
ii node-normalize-package-data 8.0.0+~2.4.4-3
ii node-npm-bundled 2.0.1-2
ii node-npm-package-arg 13.0.2+~6.1.0-3
ii node-npm-run-path [node-path-key] 6.0.0+~cs4.4.0-1
ii node-npmlog 7.0.1+~4.1.4-1
ii node-p-map 4.0.0+~3.1.0+~3.0.1-2
ii node-path-scurry 2.0.2-2
ii node-process 0.11.10-3
ii node-promise-retry 2.0.1-4
ii node-promzard 3.0.1-1
ii node-read 5.0.1-4
ii node-read-package-json [node-npm-normalize- 5.0.2+~2.0.0-5
package-bin]
ii node-resolve-import [node-walk-up-path] 2.4.0+~4.0.0-2
ii node-semver 7.7.4+~cs9.7.4-1
ii node-shebang-command [node-shebang-regex] 2.0.0+~cs4.0.0-1
ii node-socks 2.8.8-1
ii node-ssri 9.0.1-3
ii node-string-width [node-emoji-regex] 4.2.3+~cs13.2.3-1
ii node-strip-ansi 7.2.0+~cs7.0.1-1
ii node-tar 6.2.1+ds1+~cs6.1.13-10
ii node-text-table 0.2.0-5
ii node-undici 7.24.6+dfsg+~cs3.2.0-3
ii node-validate-npm-package-license 3.0.4-3
ii node-validate-npm-package-name 5.0.0+~4.0.0-1
ii node-which 2.0.2+~cs1.3.2-5
ii node-wrap-ansi 8.0.1+~8.0.1-3
ii node-write-file-atomic 7.0.1+~4.0.3-1
ii node-yallist 5.0.0-1
ii nodejs 24.17.0+dfsg+~cs24.13.2-1
Versions of packages npm recommends:
ii git 1:2.53.0+next.20260227-1
pn node-tap <none>
npm suggests no packages.
- -- no debconf information
With npm version 11.16.0+ds2-3, I believe I no longer see this issue again. Not sure why though.