You are not logged in.

#1 2017-07-12 15:20:02

GartenEden
Member
From: Germany
Registered: 2016-04-10
Posts: 10

npm 5.2.0 errer: "cb() never called!"

Upgrading to npm 5.2.0 today resulted in npm not being able to find a file whenever I run a npm command, with or without -g.
E.g.

npm out -g                                                       
Unhandled rejection Error: ENOENT: no such file or directory, stat '/build/npm/src/npm-5.2.0/npm-5.2.0.tgz'

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/eddie/.npm/_logs/2017-07-12T14_43_33_030Z-debug.log

This is my npm -versions output:

{ npm: '5.2.0',
  ares: '1.12.0',
  cldr: '31.0.1',
  http_parser: '2.7.1',
  icu: '59.1',
  modules: '57',
  node: '8.1.4',
  openssl: '1.0.2l',
  tz: '2017b',
  unicode: '9.0',
  uv: '1.13.1',
  v8: '5.8.283.41',
  zlib: '1.2.11' }

Everything worked with npm 4.6.1 before. I tried to reinstall npm through pacman, no luck tough.

Offline

#2 2017-07-14 15:41:52

GartenEden
Member
From: Germany
Registered: 2016-04-10
Posts: 10

Re: npm 5.2.0 errer: "cb() never called!"

This remains unchanged with 5.3.0.

Offline

#3 2017-07-15 04:54:58

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: npm 5.2.0 errer: "cb() never called!"

Did you ever report a bug? You can't expect issues to automagically fix themselves...

Offline

#4 2017-07-15 05:09:28

GartenEden
Member
From: Germany
Registered: 2016-04-10
Posts: 10

Re: npm 5.2.0 errer: "cb() never called!"

No, I haven't. In fact, I've never noticed the "Bugs" link in the header of this site. I thought, also due to the amount of similar questions here, that this forum is the way to go. Sorry for that.

I am surprised nevertheless that I seem to be the only Archer to have this problem. Upstream (Github Issues) there are some reports of similar problems but turn out to have different reasons. Actually, this look like a packaging problem to me.

Offline

#5 2017-07-15 12:05:13

r3b311i0n
Member
From: Sri Lanka
Registered: 2016-04-06
Posts: 26
Website

Re: npm 5.2.0 errer: "cb() never called!"

I got a similar sort of issue today:

npm outdated -g

Unhandled rejection Error: ENOENT: no such file or directory, stat '/src/semver-5.3.0.tgz'

Unhandled rejection Error: ENOENT: no such file or directory, stat '/build/npm/src/npm-5.3.0/npm-5.3.0.tgz'

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/r3b311i0n/.npm/_logs/2017-07-15T11_54_25_938Z-debug.log

What I did was install both npm and semver through npm itself, and it seems to be working fine for now.

sudo npm i -g npm semver
npm outdated -g

Package       Current  Wanted  Latest  Location
@angular/cli    1.2.0   1.2.1   1.2.1
electron       1.6.11   1.7.4  1.6.11
postcss-cli     3.2.0   3.2.0   4.1.0
serve           5.2.4   5.2.4   6.0.2

Offline

#6 2017-07-23 19:10:28

chafic
Member
From: Lebanon
Registered: 2016-01-25
Posts: 2
Website

Re: npm 5.2.0 errer: "cb() never called!"

Thanks r3b311i0n. This fixed the issue for me.

Offline

#7 2017-07-24 07:28:26

r3b311i0n
Member
From: Sri Lanka
Registered: 2016-04-06
Posts: 26
Website

Re: npm 5.2.0 errer: "cb() never called!"

Glad it worked for you @chafic

Offline

Board footer

Powered by FluxBB