npm ERR! cb() never called!

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

I also encountered the same error on:
Node v14 and v12 alpine on docker
NPM v6.14.8

I have similar issue while trying to use create-react-app.
node v14.13.1
npm v6.14.8

is there a possible fix for this error.

Also in 7.0.0-rc.3 see https://github.com/nodejs/node-addon-examples/runs/1233932860 .
Can reproduce 100%

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

@lewsea try removing node & npm completely and re-install. see if that fixes the issue.

@detj

@detj already did that 😑 but still get the same error

@lewsea

@lewsea can you try npm install -g npm@next-7 and see if that works?

Same here. Trying to run this command:
c:\ npm adduser --registry https://pkg.domain.io

npm ERR! cb() never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://npm.community>
npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\UserName\AppData\Roaming\npm-cache\_logs\2020-10-14T13_54_09_249Z-debug.log
npm -v : 6.14.8

node -v: v14.5.0

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...

npm cache verify this fixed this problem for me

the same issue tried all above all solutions but still same error

ignore my previous comment about npm cache verify , i just got lucky while installing (1600-1700 packages)


                                     
                                      this seems to have something with network state and/or network tools (bunch of errors while trying
                                      
                                       yarn install
                                      
                                      might be a hint); i've disabled little snitch and adguard also switched to cell hotspot, and installation worked (don't have time to experiment further, deadline is tomorrow xD)

@kaznovac

@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. Disconnecting from it and having a good network connection fixed it for me.

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 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 Module not found: Error: Can't resolve 'C:\Users\ELIAS MWITA NSONGO\Desktop\projects\laravel-studying\resources\scss\app.css' in 'C:\Users\ELIAS MWITA NSONGO\Desktop\projects\laravel-studying'


                               
                                webpack compiled with 1 error

@alexcruztech Hey can you tell me how to disable it?

@Sapnajha19

@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

My 5 cents on this:


                               
                                node version: 14.19.3
                                

                                npm version: 6.14.17
                                

                                OS: Windows 2022
                               
                               
                                Not able to upgrade because of the project requirements!
                               
                               
                                I had this error when running
                               
                               
                                
                                 
                                  npm ci --no-audit
                                 
                                
                               
                               
                                Nothing helped - emptying/deleting cache, deleting node_modules, dancing rain-dances...
                               
                               
                                At the end it is about the cache, and it looks like it is about the cache path length. When I used:
                               
                               
                                
                                 
                                  npm ci --no-audit --cache D:\temp\npmcch
                                 
                                
                               
                               
                                it finally passed! So the cache is moved to
                                
                                 D:\temp\npmcch
                                
                                instead of the dfefult location. If you used
                                
                                 D:\temp\npm_cache_but_something_very_long
                                
                                for the cache path, it would again fail with the same infamous error. So, it looks like it fails when the cache is on a "long path". The windows default cache path is pretty long, so that's why it is falling when no cache parameter is given.

Navigation Menu

npm ERR! cb() never called! #1916

`3 remaining items`

`Metadata`

`Assignees`

`Labels`

`Type`

`Projects`

`Milestone`

`Relationships`

`Development`

npm ERR! cb() never called! #1916

mohemos commented on Oct 9, 2020

jrcity commented on Oct 9, 2020

gengjiawen commented on Oct 10, 2020

detj commented on Oct 10, 2020

lewsea commented on Oct 12, 2020

detj commented on Oct 13, 2020

lewsea commented on Oct 13, 2020

ljharb commented on Oct 13, 2020

OksXen commented on Oct 14, 2020

prKassad commented on Oct 16, 2020

kaznovac commented on Oct 22, 2020

shreeyaBuilds commented on Oct 27, 2020

3 remaining items

kaznovac commented on Oct 27, 2020

lewsea commented on Oct 28, 2020

mrpickles3rd commented on Dec 11, 2020

indietato commented on Mar 25, 2021

GourabSanyal commented on May 6, 2021

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`prKassad commented on Oct 16, 2020`

`kaznovac commented on Oct 22, 2020`

`shreeyaBuilds commented on Oct 27, 2020`

`3 remaining items`

`kaznovac commented on Oct 27, 2020`

`lewsea commented on Oct 28, 2020`

`mrpickles3rd commented on Dec 11, 2020`

`indietato commented on Mar 25, 2021`

`GourabSanyal commented on May 6, 2021`

`Metadata`

`Metadata`

`Assignees`

`Labels`

`Type`

`Projects`

`Milestone`

`Relationships`

`Development`

`Issue actions`