cb() never called error


(Wang Dàpéng) #1

Hi I got this error on ci server today:

+ npm ci
npm ERR! cb() never called!

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

version info:

2 info using npm@6.7.0
3 info using node@v10.12.0

I’ve read a lot of topics in this forum, it seems there should be other errors along with this, like EACCES, but in my case, there is no more errors.


(Atrian Wagner) #2

The cb() error you are seeing has a thread over here:

There’s a Canary build that should give you a more descriptive error to try to better pinpoint the actual issue.


(Wang Dàpéng) #3

Hi, I’ve read the thread, but I think the canary build mentioned there is before 6.7.0 (according to the time)


(Atrian Wagner) #4

You’re right. It was fixed in 6.6.0. Are you able to provide a debug log? If so, please put it in [crash] npm ERR! cb() never called!


(Wang Dàpéng) #5

I’ve attached the debug log there: [crash] npm ERR! cb() never called!


(Thomas Nilefalk) #6

I did get this today with npm 6.8.0. In the output before the error I also have an access error:

Unhandled rejection Error: EACCES: permission denied, open '/home/thoni/.npm/_cacache/...

So it looks like what @lunitaire mentioned in the quote, cb never called after some errors, might be true.

I got this by aborting a sudo npm ... that probably gave some cached file the wrong permissions.


(system) closed #7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.