-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm ERR! cb() never called! #1916
Comments
I also encountered the same error on: |
Also in |
Can confirm that this worked for following environment. Commands executed $ mkdir cra-try
$ cd cra-try
$ npx create-react-app . Environment details $ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"
$ npx --version
7.0.0-rc.3
$ node --version
v12.19.0 |
man i just wanted to code and have a job..... now my computer is broken because of this problem ,probably because of all the things ive done/downloaded etc. lol |
@lewsea try removing node & npm completely and re-install. see if that fixes the issue. |
@detj already did that 😑 but still get the same error |
@lewsea can you try |
Same here. Trying to run this command:
npm -v : 6.14.8 |
Sometimes I see the same error on Win10 / Node14.13.1 / Npm7. I was deleting all cache, reinstalling nodejs and npm, but error is still there. It may be related to an unstable network connection... |
|
the same issue tried all above all solutions but still same error |
@Shreeyag29 it do be like that sometimes |
Same error here trying to install some pre-edited bootswatch theme to work with. That's the log, also made a cache verify and such. Still not working. |
Node v14.14.0 Facing this error when running the command 'npm outdated' npm ERR! cb() never called! npm ERR! This is an error with npm itself. Please report this error at: |
ignore my previous comment about this seems to have something with network state and/or network tools (bunch of errors while trying |
@kaznovac yeah i think it has something to do with network/firewalls and antivirus software, good thing it worked for you |
I had the same issue when I was connected to a slow VPN, 4 or 5 time it errored. |
Hi guys, I had the same issue and I finally found the problem, the problem is the antivirus, I disabled it that worked. |
Faced the same error. Was stuck with it for a long time. My os is windows 10 pro. This is how I got out of it :
I don't know why but the last two methods worked only when I deleted the logs first. Hope this works for you. |
I built my apps with Docker Compose, and each Nodejs service ended with an error: "npm error cb() never called!". I have tried everything: cache cleaning, reinstall, etc. The interesting thing is that everything works on my Macbook. So, I thought it must be something with a network or Windows. So, I decided to go via VPN, and it worked. I don't know the exact problem it solves, but this thing worked for me. |
man every time there's a new comment here, it brings back the nightmare this problem has caused. |
no answer at all |
i face the same error when i want to create the my application |
ERROR in /js/app webpack compiled with 1 error |
@alexcruztech Hey can you tell me how to disable it? |
@Sapnajha19 Hey sorry for the late answer, I think I was using Avast, so I just uninstalled and that works for me. |
There is a high probability that there has some packages incompatible with nodejs or npm version。I solved this problem when I use yarn and yarn told me more details about the incompatible version.Finally I use nvm to manage the node version and npm install successfully |
I want to install create-react-app but bump along with this bug, i have tried many solutions/articles and in stack overflow like, cache verify, cache cleaning, and many stuffs but still making this error, any help for this problem ?
2020-10-07T11_11_07_015Z-debug.log
node -v
v12.19.0
npm -v
6.14.8
The text was updated successfully, but these errors were encountered: