Closed cofuente closed 3 years ago
Closing: We suspect this has to do with a combination of resource constraints within the device/program being used and the large amount of transient dependencies being installed by this command.
We've opened https://github.com/npm/statusboard/issues/395 for us to look deeper into this and track the discussion and fixes around it. You can also read [this document](https://github.com/npm/cli/wiki/%22cb()-never-called%3F-Exit-handler-never-called%3F-I'm-having-the-same-problem!%22) for more information on why this issue might be happening currently and ways to debug it.
Is there an existing issue for this?
Current Behavior
After running the global update command from terminal I was prompted to update manually which led to the following
npm ERR! cb() never called!
error:Debug log reads as follows:
Expected Behavior
Expected packages to update with no error or at the very least have the error handling indicate which package was missing the cb().
Steps To Reproduce
Environment