npm ERR cb() never called

If you have npm version 5 or above, try this first:

$ sudo npm cache verify

Otherwise:

$ sudo npm cache clean

My node and npm versions are:

$ node -v
v0.10.0

$ npm -v
1.2.14

https://docs.npmjs.com/cli/cache

---

For anyone hitting this page around Sept 29th, 2013, there's a closed bug in Node.js 0.10.19 which is causing this error.

https://github.com/isaacs/npm/issues/2907#issuecomment-15215278 https://github.com/joyent/node/issues/6263#issuecomment-25113849

If you're on Heroku you should upgrade to 0.10.20

"engines": {
    "node": "0.10.20"
}

---

Try

sudo npm cache clean --force

More info refer: https://reactgo.com/npm-err-cb-never-called/

---

If you have updated angular cli, npm, node, you don't need to do anything more. Just run the command below to resolve the issue. This command also resolves the issue of "unexpected end of line".

npm install --no-package-lock

---

IMPORTANT! The solution below is now regarded as unstable, and you should use Node Version Management instead: Node Version Manager on Github. David Walsh also has a good introduction to NVM. NVM works beautifully and I've been using it to manage legacy WordPress projects for a few years.

Please don't use this - use NVM

I just had this exactly issue when trying to install the Sage theme for WordPress. When I ran npm install on the theme directory, it failed.

Looking in the dependencies in package.json, I could see that the engine I was running for Node was out of date. Running node -v on the command line showed that I was on v0.10.9, and the latest version of Sage requires >= 0.12.0

So here's the fix for that. These steps are from David Walsh's blog

Clear your npm cache: sudo npm cache clean -f Install the latest version of the Node helper: sudo npm install -g n Tell the helper (n) to install the latest stable version of Node: sudo n stable

You should then get a progress display, after which you will be up to date.

When I ran npm install after doing this, everything worked fine, and I was able to run gulp to build the initial dist directory.

---

Do you have a specific version of "npm" specified under "engines" in your package.json? Sounds like NPM v1.2.15 resolved the issue (and Heroku has available). I was getting the same problem with "1.1.x".

---

Run npm install -g npm

Then run npm install

---

Updating the NodeJS https://nodejs.org/en/ Fixed My Issue.

Run npm install -g npm & npm cache clean

---

For me none of the above solutions worked (reinstalling, clearing cache, folders etc.).

My problem was solved with:

npm config set registry https://registry.npmjs.org/

---

UPDATED: The problem is pretty common here is the new fix npm cache verify run that you will be good to go!

---

I had the same problem while installing ionic@beta. I tried the following items and they didn't help me.

npm cache clean Manually delete cache from %temp%\npm-* Command prompt "Run As Administrator"

I solved the problem by installing node-v5.10.1-x64.msi (Previous version was node-v5.9.0-x64.msi) and run an npm cache clean before installing ionic@beta

It worked!

---

Since NPM 6 you can do a clean install. That was the only solution which worked for me.

Just run the following:

npm clean-install

Notes:

You might also manually remove the node_modules folder and try again in case the command above failed.

If still doesn't work, the global cache might be broken, try running npm cache clean --force and then do a clean install.

The clean-install command works on npm 6 and above. For older versions consider checking the other answers below.

---

[Works] try

npm config delete https-proxy

it would have conflicted with proxy.

---

I had the same problem with NPM version 1.3.11, and solved it simply by re-running the exact same command multiple times ("npm update -g" in my case). The error popped up for a different package on each subsequent run and eventually everything updated successfully.

For me at least, it seems like it was being caused by a network issue (corrupted downloads). I was also getting an error about an invalid package, which I was able to resolve by deleting all instances of "tmp.tgz".

Edit: (Probably unrelated, but in case this helps anyone: I was using Windows, and started a command prompt as an Administrator after receiving the initial error).

---

I had the cb() never called! error, and none of the answers here directly worked for me. I was running Node v8.11.2, and I had to manually delete the package-lock.json file to get anywhere. After doing this, I ran npm cache verify per what some of the answers recommended. Then, running npm i yielded the following result:

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN securities-stub@1.0.0 No description
npm WARN securities-stub@1.0.0 No repository field.

up to date in 5.118s

---

As of March 2021 the new NPM version fixes many of those issues.

So calling npm i -g npm@latest fixes this again (In between this did not work).

---

If the bug persists even after running npm cache clean --force, try to rerun npx create-react-app your_app_name after switching to a different network. This error could also cause due to slow and unstable networks...

---

I just globally installed the newest version of NPM and it worked for me. I guess Clearing npm cache is optional.

npm install -g npm

---

For me on npm 6.4.0 and node 10.9.0 none of the answers worked. Reinstalled node, npm, cleaned cache, removed folders ...

After some debugging it turned out I used npm link for two of my modules under development to link to each other. Once I removed and redid some linking I was able to get it all working again.

---

Knowing that this is an old question and many of you had provided your answers. Just to share my experience with this error and how I fixed.

This all started after I upgrade my Node version to > 12, I did go through all the answers and try to follow steps clearing npm Cache, deleting the node_modules folder. No one of them resolve my problem.

The root cause in my case was proxy restricting installation. I deleted the proxy settings to fix the problem.

Check if you have any proxy config npm config list Delete them by npm config delete proxy npm config delete http-proxy npm config delete https-proxy Now try npm install

---

What worked for me was: delete the package-lock.json file and run the following command:

npm cache clean --force

---

sudo npm cache clean didn't work out for me. Update to the latest version of node helps.

I had node v.5.91 and updated to v6.9.1

---

I suggest: Switch to Yarn! - Yarn is a package manager which uses the same package.json file and node_modules folder as npm.

With npm I had the same problem: On a CentOS 6 install I got the ERR cb() never called error repeatedly and could not find a way to make npm reliably complete installation of some packages (like webpack for example). - Yarn works flawlessly, even on flaky network connections.

Migration to Yarn is easy. Most subcommands are the same. They have a good Migration guide. Read on to the handy CLI commands comparison at the end.

---

I have the same error in my project. I am working on isolated intranet so my solution was following:

run npm clean cache --force

delete package-lock.json

in my case I had to setup NPM proxy in .npmrc

---

Try switching your network, somehow switching network worked for me.

I have tried many things mentioned in other answers, like:

npm cache clean --force Delete existing node_modules, delete package-lock.json, and reinstall using - npm i npm cache verify npm clean-install

None of the above worked for me, might work for you. Try your luck.

---

It appears that particular dependency versions can cause this issue. For example, gulp-uglifycss 1.0.7 has this problem (see https://github.com/rezzza/gulp-uglifycss/issues/15).

If you are allowing major or minor version updates in your packages.json via ^ or ~, remove those characters thoughout the file and try another npm install. If it works that time then you'll be alright after you have the fun of narrowing down which package is causing the problem.

---

I had the same issue while trying to install firebase-tools in my windows laptop. this is how i solved it.

I downloaded kaspersky and installed it. then i disabled kaspersky secure connections i opened cmd and run this command npm cache clean --force i then run this command npm install npm@latest -g i then run the firebase cli command npm install -g firebase-tools

---

For Ubuntu Users, the given below method worked for me.

Firstly, perform this : sudo npm cache verify

Then go to Home->.npm and delete the _cache folder by : sudo rm -rf _cacache/

go and check, maybe you found the solution.

---

I too faced the same problem today as I force stopped the npm package download in between due to internet issues.

I tried various things like,

Running sudo npm cache clean -f - which did not work as expected Clean uninstalling node and reinstalling it - which as well didn't work

I finally tried to delete the folder containing the npm cache that was creating the problem. I ran the following command,

sudo rm -rf /Users/{user_system_user}/.npm/

Then I tried installing the package that was stuck and everything worked like a charm.

P.S: replace {user_sytem_user} according to the current user of your system.

---

If you are open your code in a IDE such as IntelliJ idea Close it and re try

---