GithubApp: error cb() never called!

What I Wanted to Do

I was trying to make an npm install of an example application extracted from Github

What Happened Instead

Got an error:

pmoura@Ubuntu18:~/app/fabric-application-examples/contracts/cp-ts-extended$ npm i
npm ERR! cb() never called!

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

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pmoura/.npm/_logs/2019-03-27T09_40_02_282Z-debug.log
pmoura@Ubuntu18:~/app/fabric-application-examples/contracts/cp-ts-extended$

Reproduction Steps

I just did npm i

Details

Log file: 2019-03-27T09_40_02_282Z-debug.log (327.4 KB)

Platform Info

$ npm --versions
6.4.1
$ node -p process.platform
linux

Hi @pmoura11! The “ERR! cb() never called!” is not the underlying error, which is not being displayed for you. There were fixes in npm 6.6.0 to improve the display of the underlying error, so I suggest you update your npm and then hopefully you will be shown what the problem is.

After upgrading to npm@6.6.0, I still getting the same error:

pmoura@Ubuntu18:~/app/fabric-application-examples/contracts/cp-ts-extended$ npm i
npm ERR! cb() never called!

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

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pmoura/.npm/_logs/2019-03-27T10_46_17_108Z-debug.log
pmoura@Ubuntu18:~/app/fabric-application-examples/contracts/cp-ts-extended$ npm -v
6.6.0

2019-03-27T10_46_17_108Z-debug.log (327.3 KB)

(Oh, that was disappointing! I don’t have another suggestion.)

i am experincing this error as well while attempting to install the MEAN stack 2019-06-04T23_11_12_005Z-debug.log (864.9 KB)

I got the same issue… cb() not calling with permission.
It happen when I upgraded from npm 6.9.0 to 6.10.0

I checked the log, no help mentioning to share the report to npm.

I resolved the issue myself:

I went to error directly checked file permission, it was assigned to root.
I changed the permission and run the command again and its worked.

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