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" Error thrown in case of a proxy authentication error #544

Closed
andy-schulz opened this issue Dec 2, 2019 · 1 comment
Labels
Bug thing that needs fixing

Comments

@andy-schulz
Copy link

What / Why

I am behind an authenticated corporate proxy.

To set the proxy i am using

npm config set proxy http://username:password@proxy.company.com
npm config set https-proxy http://username:password@proxy.company.com

I had to reset the passord but forgot to reset it for npm.

When running:

npm install

npm responded with the error

 error cb() never called!

Changing the password with npm config set proxy fixed the problem.

Where

  • Windows 10 VM
  • npm@6.13.1
  • node@v10.15.3

Current Behavior

npm install throws error cb() never called!

Expected Behavior

I would like to see a 407 Proxy Authentication Error printed to console and not just to the log.

Log

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\MYFOLDER\\nodejs\\node.exe',
1 verbose cli   'C:\\MYFOLDER\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'update' ]
2 info using npm@6.13.1
3 info using node@v10.15.3
4 verbose npm-session 66cb6a3319a6069e
5 verbose update computing outdated modules to update
6 http fetch GET 407 https://registry.npmjs.org/@thekla%2fconfig 365ms
7 http fetch GET 407 https://registry.npmjs.org/@thekla%2fcore 364ms
8 http fetch GET 407 https://registry.npmjs.org/del-cli 392ms
9 http fetch GET 407 https://registry.npmjs.org/@thekla%2fweb-and-mobile-abilities 425ms
10 http fetch GET 407 https://registry.npmjs.org/cucumber-html-reporter 446ms
11 http fetch GET 407 https://registry.npmjs.org/npm 667ms
12 http fetch GET 407 https://registry.npmjs.org/thekla 1061ms
13 http fetch GET 407 https://registry.npmjs.org/eslint-plugin-standard 1149ms
14 http fetch GET 407 https://registry.npmjs.org/eslint-plugin-node 1357ms
15 http fetch GET 407 https://registry.npmjs.org/eslint-config-standard 1358ms
16 http fetch GET 407 https://registry.npmjs.org/eslint-plugin-import 1472ms
17 http fetch GET 407 https://registry.npmjs.org/junit-report-builder 1637ms
18 http fetch GET 407 https://registry.npmjs.org/eslint-plugin-promise 1854ms
19 http fetch GET 407 https://registry.npmjs.org/typescript 1884ms
20 http fetch GET 407 https://registry.npmjs.org/@typescript-eslint%2fparser 2157ms
21 http fetch GET 407 https://registry.npmjs.org/@typescript-eslint%2feslint-plugin 2277ms
22 http fetch GET 407 https://registry.npmjs.org/log4js 2283ms
23 http fetch GET 407 https://registry.npmjs.org/eslint 2286ms
24 timing npm Completed in 4030ms
25 error cb() never called!
26 error This is an error with npm itself. Please report this error at:
27 error <https://npm.community>
@andy-schulz andy-schulz changed the title [BUG] "npm ERR! cb() never called" Error thrown in case of an proxy authentication error [BUG] "npm ERR! cb() never called" Error thrown in case of a proxy authentication error Dec 2, 2019
@mikemimik mikemimik added Bug thing that needs fixing Community labels Jan 20, 2020
@mikemimik
Copy link
Contributor

Duplicate issue; aggregating into #417.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing
Projects
None yet
Development

No branches or pull requests

2 participants