Resolving npm ERR! cb() never called errors

This was one extremely annoying error that we kept encountering when trying to update existing node packages using the Node Package Manager from the command line:

npm ERR! cb() never called!

After much googling (interrupted by intermittent bouts of swearing at the computer) we finally found a solution to the problem.

Delete and try again

Now there may have been a less drastic solution (such as changing ownership of the .npm directory for example - which is an approach we only thought of later on post-solution) but after trying the following:

npm cache clean

And finding not one single improvement in the situation we opted to simply remove the .npm folder from our home directory like so:

Categories

Post a comment

All comments are welcome and the rules are simple - be nice and do NOT engage in trolling, spamming, abusiveness or illegal behaviour. If you fail to observe these rules you will be permanently banned from being able to comment.

You might also like...

If you don’t have administrator access to your Mac and need to perform tasks such as installing software then you’ll need to acquire root access. To do this is relatively simple, just follow the steps outlined below and you should be up and running in the space of 3 minutes or less: