[Error] cb() never called! on Windows 10 #722

Comments

yuvipatel commented Jan 23, 2020 •

While executing ‘npm install‘ of my project got below error —

«npm ERR! cb() never called!»

My node and npm version details are—
node — v13.6.0
npm — 6.13.4

System Information —
Operating System: Win64
Chrome Browser Version: 79.0.3945.130
Chrome OS Version: NA
Memory: 1.01GB available out of 8.45GBCPU: Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz ( x86_64architecture — 8 processors )

The text was updated successfully, but these errors were encountered:

ljharb commented Jan 23, 2020

SimonMaghiar commented Nov 25, 2020

Jeez can’t believe that no one found the solution to this problem.

Tomato6966 commented Dec 17, 2020

First use this: npm cache clean —force

Then it should work!

rvinothkumarer commented Dec 18, 2020 •

Hi @Tomato6966 — Im using the configurations as below and tried all the ways suggested but still facing the same. Im running behind the corporate proxy. If i remove the npm proxy from config, it throws error related to proxy. If i add the proxy then it throws the cb() never called error. Any help would be much appreciated.

npm cache clean —force —>doesnt work

npm cache verify —> doesnt work

npm install -g @angular/cli
npm ERR! cb() never called!

npm install: «cb() never called» #17839

Comments

daaang commented Jul 18, 2017 •

I’m opening this issue because:

• npm is crashing.
• npm is producing an incorrect install.
• npm is doing something I don’t understand.
• Other: the error output specifically asked me to report it, and I couldn’t find a duplicate.

What’s going wrong?

My local npm install was working until today, but now it will not install anything. It complains of a nonpermitted cross-device link and that cb() is never called.

Note: I’ve replaced some specific paths with $HOME and $PREFIX to avoid cluttering this up with my environment details. The important points are that (a) I don’t have root access to this machine, (b) this is a local install of node and npm, and (c) $HOME and $PREFIX exist on different drives.

How can the CLI team reproduce the problem?

I’ve completely uninstalled, recompiled, and reinstalled node, and this still happens. My installation procedure looked like this:

To be clear, this error appears no matter what I try and install, regardless of whether I add the -g flag.

supporting information:

• npm -v prints: 5.0.3
• node -v prints: v8.1.4
• npm config get registry prints: https://registry.npmjs.org/
• Windows, OS X/macOS, or Linux?: Debian GNU/Linux 8.8 (jessie) (3.16.0-4-amd64)
• Network issues: N/A
• Container: N/A

The text was updated successfully, but these errors were encountered:

beansprout commented Jul 20, 2017

I get very similar error messages except I am trying to update using homebrew.
I ran this: brew update && brew upgrade node && npm update -g npm

Updating homebrew produced no issues. This printed after the updating:

(Note) I ended up installing the updates with the mac install pkg which installed fine.

nunoarruda commented Jul 20, 2017 •

Similar issue here when trying to list outdated packages:

j2l commented Jul 20, 2017 •

Same here,
And cache clean —force before didn’t fix it:

EDIT: fix in #17222 worked for me:
npm i -g MODULE
npm un -g MODULE
npm i -g MODULE (again)

kenashworth commented Jul 20, 2017

This was working (I think) before I homebrew updated node to 8.2.0.sierra.

kenashworth commented Jul 20, 2017

interestingly, my error has Unhandled rejection Error: ENOENT: no such file or directory, stat ‘/Users/Users/brew/Library. (double Users) when run from not

1 of 13 tasks complete

daaang commented Jul 21, 2017

As long as I install a version of node bundled with a version of npm less than 5, npm works as I’d expect it to. I can even run npm i -g npm , but, if I do, it will be npm’s last successful run.

I can make do with npm 4.1.2 until this gets fixed, though. In the meantime, I’d be happy to test-run things and report on them, if anybody’s having trouble reproducing this.

nunoarruda commented Jul 21, 2017 •

I’m no longer experiencing this issue with Node v8.2.1, not sure if/how is it related.

marcoose777 commented Jul 25, 2017

Me too,
Just started today. Daangs suggestion cleared one of the errors up with the package semver, but the apm(atom package manager) problem is persistent(see bellow).

Error: cb() never called! #16551

Comments

karamanolev commented May 6, 2017 •

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?

How can the CLI team reproduce the problem?

Not sure what the repro is. I got the error, Googled a bit, found some tips, ran

Upgraded node, npm to latest versions and got the same thing. I also tried npm version 3.10.10. Here’s a gist of the debug log: https://gist.github.com/karamanolev/db323c39deca4d73de995e508055c6cd
Here’s a gist of my package.json: https://gist.github.com/karamanolev/77e3f23c7728bbb46ad7ff436905d766
Everything worked very well for a long time. Today I just had to do npm install due to some new versions in our package.json.

supporting information:

OS: macOS
npm installed via nvm

• Geographic location where npm was run: Bulgaria
• I use a proxy to connect to the npm registry.
• I use a proxy to connect to the web.
• I use a proxy when downloading Git repos.
• I access the npm registry via a VPN
• I don’t use a proxy, but have limited or unreliable internet access.
• Container:
  • I develop using Vagrant on Windows.
  • I develop using Vagrant on OS X or Linux.
  • I develop / deploy using Docker.
  • I deploy to a PaaS (Triton, Heroku).

The text was updated successfully, but these errors were encountered:

«npm ERR! cb() never called!» #417

Comments

darcyclarke commented Nov 8, 2019 •

*Updated* as of 01/15/2021

Note: Please read this doc before filing a new issue or adding a comment to this thread.

The text was updated successfully, but these errors were encountered:

DanielRuf commented Nov 11, 2019

I think we have many reports of the same so these should all be duplicates.

Afaik this is resolved by force-clearing the cache and upgrading / updating to the latest npm version.

DanielRuf commented Nov 11, 2019 •

ruyadorno commented Nov 11, 2019

thanks @DanielRuf for linking all those ❤️

ruyadorno commented Nov 19, 2019

DanielRuf commented Dec 8, 2019 •

DanielRuf commented Dec 25, 2019

I guess we can check which version first introduced this (doing a small git bisect ) and check the stacktraces for similarities.

DanielRuf commented Dec 25, 2019

Following versions were mentioned in the issues:

Now trying to get a reproducible testcase.

DanielRuf commented Dec 25, 2019

Relevant changes in the past tolog this error: npm/npm#15716

DanielRuf commented Dec 25, 2019 •

Tests with a local npm 6.13.1 (on macOS):

@vue/cli : not reproducible
npm audit fix : not reproducible
plotly.js : not reproducible
expo-cli : not reproducible

So far it looks like this is caused by other errors which cancel the CLI too early.

I remember that we had this bug also on Ubuntu with the latest version and some packages.

melvinwallerjr commented Jan 4, 2020 •

I’m experiencing the same error trying to install a company project for development.
Microsoft Windows [Version 10.0.17134.1184]

Using NVM to switch instances of node/npm
node v10.14.2 (64-bit), npm v6.4.1
node v12.4.0 (64-bit), npm v6.9.0

project was generated with Angular CLI version 8.3.21

[NVM for Windows Setup, Ecor Ventures LLC, ‎Tuesday, ‎August ‎7, ‎2018 9:46:31 PM]

ljharb commented Jan 4, 2020

(note that must be nvm-windows; actual nvm doesn’t work on non-WSL Windows, and doesn’t distinguish 64-bit)

mdouglass commented Jan 4, 2020 •

We’re getting this error intermittently in both local development and in our CI system. Happy to add any additional logging that might help. Attached the npm log from a run that just happened on my laptop on my mac — trying to npm install one of our private packages. Immediately re-running the command worked without issue.

❯ npm -v
6.13.4
❯ node -v
v13.5.0

Let me know if there’s anything I can do to help track this down, would like to kill the issue.

DanielRuf commented Jan 14, 2020

DanielRuf commented Jan 14, 2020

DanielRuf commented Jan 14, 2020

mikemimik commented Jan 17, 2020

• npm audit fix ( npm@6.9.0 / node@10.16.1 )
• npm install ( npm@6.10.2 / node@12.8.0 )
• sudo npm install -g npm ( npm@6.9.0 / node@x.y.z )
• n/a likely npm i ( npm@6.12.1 / node@13.1.0 ) ( npm@6.12.0 / node@12.13.0 )
• npm install ( npm@6.4.1 / node@12.13.0 )
• npm install ( npm@6.9.0 / node@10.16.1 )
• vue create ( npm@6.2.0 / node@10.9.0 )

Thoughts as triaging:

• Seems like there is an error while installing a package that causes this cb() never called! error.
• There are 42 issues to triage.
• #442 original issue references a fix which references updating and cleaning cache to solve issue (updating fixes permissions), cache might indicate problem exists/existed in cacache or pacote
• #451 seems to have same symptom but cause doesn’t seem to be within npm , though it does help point to an issue with while installing a package

theBstar commented Mar 27, 2021

I encountered this issue while running npx react-native init someProject . I was on a slow network connection and the installation got terminated midday. Running npx react-native init someProject again resulted in react-native command not found . Clearing npx cache helped. https://stackoverflow.com/questions/63510325/how-can-i-clear-the-central-cache-for-npx

SiddharthShyniben commented Mar 29, 2021

My probably-wrong hypothesis is that maybe when we terminate any action before the cb() callback gets called we have this error. As I read on the wiki, it happened because the process gets exited (by net problems, us terminating, etc.) before the callback is called. (See this wiki). I’m telling you I’m probably wrong

JayeshGohel commented Mar 30, 2021

Got npm ERR! cb() never called! while executing npm install. Any fix for this? Below is the image showing the warnings and errors I am getting

Ally4 commented Apr 1, 2021

Before the end of the process of npm install, I get this error
npm ERR! cb() never called!

mateusgms commented Apr 1, 2021

I’ve got this error trying install dependencies using yarn

MorningK commented Apr 9, 2021

I got this error when i was running npm install
node -v
v14.16.0
npm -v
6.14.11
2021-04-09T07_51_38_305Z-debug.log

bvaradha commented Apr 9, 2021

I got the same error on using this on actions on npm login. I am using mac OS as runner machine.
npm login —scope=@ —registry=https:///npm/
npm login —scope=@ —registry=https:///npm/
shell: /bin/bash -e <0>
env:
NPM_CONFIG_USERCONFIG: /Users/XXXXXXX/actions-runner/_work/_temp/.npmrc
NODE_AUTH_TOKEN: XXXXX-XXXXX-XXXXX-XXXXX
npm notice Log in on https:///npm/
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/cli/issues
2021-04-09T11:20:51.1659890Z npm ERR! cb() never called!
2021-04-09T11:20:51.1661290Z
2021-04-09T11:20:51.1663470Z npm ERR! This is an error with npm itself. Please report this error at:
2021-04-09T11:20:51.1665150Z npm ERR! https://github.com/npm/cli/issues
2021-04-09T11:20:51.1783800Z
2021-04-09T11:20:51.1785570Z npm ERR! A complete log of this run can be found in:

I am on macOS.
npm -version
7.7.6
$ node —version
v15.14.0

Prajwal-Adhav commented Apr 10, 2021 •

Updated as of 01/15/2021

Note: Please read this doc before filing a new issue or adding a comment to this thread.
Hello Everybody I am also encountering with the issue of npm ERR! cb() never called!
I will give all the possible data that I have regarding this error:-
O.S-Windows 10 Version 20H2
OS build-19042.746
npm version-v6.14.12
Node version-v14.16.1
While I was trying to download an external dependency for a React Web application I typed «npm install» in the node terminal and after some time this error popped up. This error tells that there is an error with npm itself. Below is the screenshot and log file of the same.

swastikbiswas962 commented Apr 12, 2021

I was trying to create a React app for my personal project, but then this error pops up whenever I’m in the middle of downloading react-dom . I see several people facing this issue, so I think this is a problem with npm itself.
Please help us.

swastikbiswas962 commented Apr 12, 2021

I found a quick fix. Don’t know why it worked, but if you’re on Windows, fixing the problem is as simple as going to the Control Panel > Uninstall a program, then selecting Node.js and clicking Repair. It works!

sunshu commented Apr 15, 2021

Update npm to the latest version fixed my question