Skip to content
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

[BUG] npm ERR! cb() never called! #2338

Closed
Man-RP opened this issue Dec 12, 2020 · 3 comments
Closed

[BUG] npm ERR! cb() never called! #2338

Man-RP opened this issue Dec 12, 2020 · 3 comments
Labels
Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release

Comments

@Man-RP
Copy link

Man-RP commented Dec 12, 2020

Current Behavior:

I'm getting:

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!     ..\AppData\Roaming\npm-cache\_logs\2020-12-12T09_42_18_360Z-debug.log

when trying to npm install to complete without errors

Expected Behavior:

Finish install without errors

Steps To Reproduce:

cloned repo from gitlab and typed npm install.
tried to npm cache clean --force , clone the repo in alternative directory, reinstall node and update npm.

Environment:

  • OS: MS Windows 10
  • Node: 14.15.1
  • npm: 6.14.9

the full error log attached.
2020-12-12T09_42_18_360Z-debug.log

@Man-RP Man-RP added Bug thing that needs fixing Needs Triage needs review for next steps Release 6.x work is associated with a specific npm 6 release labels Dec 12, 2020
@eoinion
Copy link

eoinion commented Dec 16, 2020

I got this resolved on my end.
My .npmrc file had proxy and https-proxy set up, not sure how they got in there.
I commented out both lines, saved file and working again as normal.

@Tomato6966
Copy link

First use this: npm cache clean --force

Then it should work!

@Man-RP
Copy link
Author

Man-RP commented Jan 8, 2021

First use this: npm cache clean --force

Then it should work!

actually, I had mentioned I tried this on issue's details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release
Projects
None yet
Development

No branches or pull requests

4 participants