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

error cb() never called! #2352

Closed
sheikx1221 opened this issue Dec 15, 2020 · 10 comments
Closed

error cb() never called! #2352

sheikx1221 opened this issue Dec 15, 2020 · 10 comments
Labels
Bug thing that needs fixing Release 6.x work is associated with a specific npm 6 release

Comments

@sheikx1221
Copy link

Current Behavior:

Unable to Complete Installation of node modules for Nest.js Project

Expected Behavior:

Installation should be handled by npm

Steps To Reproduce:

  1. Use a nest js project
  2. npm install --verbose

Environment:

  • Node: 14.15.0
  • npm: 6.14.8
@sheikx1221 sheikx1221 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 15, 2020
@sheikx1221 sheikx1221 changed the title [BUG] <title>error cb() never called! error cb() never called! Dec 15, 2020
@eoinion
Copy link

eoinion commented Dec 15, 2020

+1, having the same issue myself when using npm login or npm install commands.
Node: 14.15.1
npm: 6.14.8

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

@DCarvalho44
Copy link

Hi, I have the same problem and I wondering if you already had solve, I already tried to clean the cache but the problem continuous, eoinion could you please explain better how you solved the problen, where i can find the .npmrc fil, thanks

@eoinion
Copy link

eoinion commented Dec 16, 2020

Hi, I have the same problem and I wondering if you already had solve, I already tried to clean the cache but the problem continuous, eoinion could you please explain better how you solved the problen, where i can find the .npmrc fil, thanks

Your .npmrc should be in your C://Users/{{account name}}

Open the file with a text editor and remove proxy entries. Save file.

@DCarvalho44
Copy link

Hi, I have the same problem and I wondering if you already had solve, I already tried to clean the cache but the problem continuous, eoinion could you please explain better how you solved the problen, where i can find the .npmrc fil, thanks

Your .npmrc should be in your C://Users/{{account name}}

Open the file with a text editor and remove proxy entries. Save file.

what happen if in the .npmrc there is only one line and it's not proxy entries.

@Tomato6966
Copy link

First use this: npm cache clean --force

Then it should work!

@swapnilbarwat
Copy link

swapnilbarwat commented Dec 21, 2020

I was facing issue on windows 10. Changing folder location from C:/folder1/react-practice/my-app to C://react-practice/my-app fixed it for me.

@rak10
Copy link

rak10 commented Jan 2, 2021

I was facing issue on windows 10. Changing folder location from C:/folder1/react-practice/my-app to C://react-practice/my-app fixed it for me.

This worked for me (nothing else did)! Thank you!

@darcyclarke darcyclarke removed the Needs Triage needs review for next steps label Feb 13, 2021
@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

@darcyclarke
Copy link
Contributor

npm v6 is no longer in active development; We will continue to push security releases to v6 at our team's discretion as-per our Support Policy.

If your bug is preproducible on v7, please re-file this issue using our new issue template.

If your issue was a feature request, please consider opening a new RRFC or RFC. If your issue was a question or other idea that was not CLI-specific, consider opening a discussion on our feedback repo

Closing: This is an automated message.

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

7 participants