Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

npm ERR! cb() never called! #18250

Closed
1 of 4 tasks
zbjumper opened this issue Aug 21, 2017 · 3 comments
Closed
1 of 4 tasks

npm ERR! cb() never called! #18250

zbjumper opened this issue Aug 21, 2017 · 3 comments

Comments

@zbjumper
Copy link

I'm opening this issue because:

  • npm is crashing.
  • npm is producing an incorrect install.
  • npm is doing something I don't understand.
  • Other (see below for feature requests):

What's going wrong?

When I run "npm update", it Crashed! The Log is :

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/npm/issues

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/Bill/.npm/_logs/2017-08-21T10_06_07_863Z-debug.log

log file is :

2017-08-21T10_06_07_863Z-debug.log.zip

@kenany kenany added the support label Aug 21, 2017
@daankets
Copy link

I have exactly the same issue with npm install and npm prune --production. There is no logfile generated.

@npm-robot
Copy link

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining WeAllJS and asking your question in its #npm channel. The npm CLI team is all present there, but there are also lots of other folks who can help you too.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

@salmanwaheed
Copy link

salmanwaheed commented Oct 27, 2017 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants