npm / npm/cli

2025-10-16T04_02_49_901Z-debug.log

Open
#8,679 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
10.1k
Forks
4.7k
Avg merge
2d 2h
Merged PRs (30d)
19

Description

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at: npm ERR! https://github.com/npm/cli/issues

verbose cli [
0 verbose cli '/usr/bin/node',
0 verbose cli '/usr/lib/node_modules/npm/bin/>
0 verbose cli 'exec',
0 verbose cli '--',
0 verbose cli 'auth',
0 verbose cli 'secret'
0 verbose cli ]
1 info using npm@7.17.0
2 info using node@v14.21.3
3 timing npm:load:whichnode Completed in 29ms
4 timing config:load:defaults Completed in 56ms
5 timing config:load:file:/usr/lib/node_modules>
6 timing config:load:builtin Completed in 51ms
7 timing config:load:cli Completed in 77ms
8 timing config:load:env Completed in 7ms
9 timing config:load:file:/root/ish/ios-siem/.n>
10 timing config:load:project Completed in 70ms
11 timing config:load:file:/root/.npmrc Complet>
12 timing config:load:user Completed in 3ms
13 timing config:load:file:/etc/npmrc Completed>
14 timing config:load:global Completed in 2ms
15 timing config:load:validate Completed in 4ms
16 timing config:load:credentials Completed in >
17 timing config:load:setEnvs Completed in 33ms
18 timing config:load Completed in 343ms
19 timing npm:load:configload Completed in 348ms
20 timing npm:load:setTitle Completed in 3ms
21 timing npm:load:setupLog Completed in 47ms
22 timing npm:load:cleanupLog Completed in 70ms
23 timing npm:load:configScope Completed in 0ms
24 timing npm:load:projectScope Completed in 99>
25 timing npm:load Completed in 610ms
26 timing config:load:flatten Completed in 80ms
27 http fetch GET 200 https://registry.npmjs.or/>
28 timing arborist:ctor Completed in 28ms
29 timing arborist:ctor Completed in 34ms
30 timing arborist:ctor Completed in 4ms

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached debug log and reproduce the shown npm@7.17.0/node@v14.21.3 command, npm exec -- auth secret. Trace the npm CLI path that emits “cb() never called!” and establish the expected behavior; the issue is complete only when the failure cause and a verified correction are clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.