npm 6.9.0 cb() never called!

What I Wanted to Do

npm install

What Happened Instead

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://npm.community>

Reproduction Steps

Run
npm install
with the following in package.json:

  "dependencies": {
    "interweave": "^11.1.0",
    "react": "^16.8.6",
    "react-dom": "^16.8.6",
    "react-redux": "^7.1.0",
    "react-router-dom": "^5.0.1",
    "react-scripts": "3.0.1",
    "redux": "^4.0.1",
    "redux-thunk": "^2.3.0"
  },
  "devDependencies": {
    "redux-immutable-state-invariant": "^2.1.0"
  }

Details

18134 silly extract fsevents@1.2.9 extracted to C:\...\reactApp\node_modules\.staging\fsevents-f340d72b (48817ms)

18135 silly extract fsevents@1.2.9 extracted to C:\...\reactApp\node_modules\.staging\fsevents-4d0bb3b6 (36439ms)

18136 silly extract core-js-pure@3.1.3 extracted to C:\...\reactApp\node_modules\.staging\core-js-pure-18fedac0 (46082ms)

18137 silly extract core-js@3.0.1 extracted to C:\...\reactApp\node_modules\.staging\core-js-ad68f3dc (46131ms)

18138 silly extract core-js@2.6.9 extracted to C:\...\reactApp\node_modules\.staging\core-js-c7dd53e4 (42502ms)

18139 silly extract rxjs@6.5.2 extracted to C:\...\reactApp\node_modules\.staging\rxjs-e669cb3b (107933ms)

18140 timing npm Completed in 152305ms

18141 error cb() never called!

18142 error This is an error with npm itself. Please report this error at:

18143 error <https://npm.community>

Platform Info

$ npm --versions
{
  reactApp: '0.1.0'
  npm: '6.9.0',
  ares: '1.15.0',
  brotli: '1.0.7',
  cldr: '35.1',
  http_parser: '2.8.0',
  icu: '64.2',
  llhttp: '1.1.3',
  modules: '72',
  napi: '4',
  nghttp2: '1.38.0',
  node: '12.4.0',
  openssl: '1.1.1b',
  tz: '2019a',
  unicode: '12.1',
  uv: '1.29.1',
  v8: '7.4.288.27-node.18',
  zlib: '1.2.11'
}
$ node -p process.platform
win32

Unfortunately the “error cb() never called!” is a generic error and does not tell us what actually went wrong. Hopefully someone recognises the situation.

I tried producing on Mac and it installed ok (with 200 MB installed to node_modules).

My only guess is, do you have git command available on command line?

I see exactly the same problem (but with a different package.json file).

This is on a new laptop (fresh Windows 10 installation) with a fresh installation of Node.js. Here are my versions:

{
  'local-ui': '0.0.0',
  npm: '6.9.0',
  ares: '1.15.0',
  brotli: '1.0.7',
  cldr: '35.1',
  http_parser: '2.8.0',
  icu: '64.2',
  llhttp: '1.1.3',
  modules: '72',
  napi: '4',
  nghttp2: '1.38.0',
  node: '12.4.0',
  openssl: '1.1.1b',
  tz: '2019a',
  unicode: '12.1',
  uv: '1.29.1',
  v8: '7.4.288.27-node.18',
  zlib: '1.2.11'
}

The same package.json file works on another laptop with an older setup.

I looked at many other threads and none of the suggested solutions helped.

Here is my logfile. Note that it does not contain any other error details:
2019-06-17T07_16_03_144Z-debug.log (643.6 KB)

@shadowspawn in my case git is available from the command line.

1 Like

Looks like I found the issue (at least for my case):
I do have an alternative registry configured in .npmrc which is only accessible via VPN. I didn’t have the VPN connection enabled. Looks like this caused my troubles.

I think the error message should be much more descriptive in this case. cb() never called was not at all helpful.