Caniuse: "cb() never called!" on NPM install (Node v5.9.1)

Created on 14 Nov 2016  ·  7Comments  ·  Source: Fyrd/caniuse

I'm running into errors installing caniuse-db from NPM as of today:

npm install caniuse-db
npm ERR! cb() never called!

I get the same with the --debug flag added, and nothing looks out of place when I call it with --verbose (although I'm not an expert here...)

I've had this issue on my local Macbook Pro (MacOS Sierra) and on our CI Server (Codeship, using CentOS 6 on Docker).

Thanks for your help, and let me know if I can help you debug this issue.

Misc. sitdata request

Most helpful comment

node: v5.9.1
npm: 3.7.3

catalin-miron npm install -g [email protected]
npm ERR! cb() never called!

node: v6.9.1
npm: 3.10.8

catalin-miron npm install -g [email protected]
/Users/catalin-miron/.nvm/versions/node/v6.9.1/lib
└── [email protected]

All 7 comments

node: v5.9.1
npm: 3.7.3

catalin-miron npm install -g [email protected]
npm ERR! cb() never called!

node: v6.9.1
npm: 3.10.8

catalin-miron npm install -g [email protected]
/Users/catalin-miron/.nvm/versions/node/v6.9.1/lib
└── [email protected]

@catalin-miron-hs Thanks - good to know it's been fixed in Node 6! Do you know what the issue is here, and whether there's a Node 5.x version that doesn't run into this issue?

@jonnyarnold the version 1.0.30000579 (one patch older) is compatible with Node 5.x

@Fyrd what version of npm did you had when publishing this package? From what I can see, you published 1.0.30000580 with npm > 3.x and 1.0.30000579 with npm < 3.x is this correct?

@catalin-miron-hs I'm not sure...I think I may have published it with another machine...didn't know that could have any side-effects. My understanding of npm publishing is pretty limited.

@Fyrd that's not a problem, after talking with @ai it seems that _node v5.x_ it's not maintained/supported by nodejs https://github.com/nodejs/LTS.
I could reproduce the bug only in node v5.9.x versions and seems legit to drop support for v5.

@catalin-miron-hs If that is the case, can I suggest leaving a v5.x compatible version available and bumping the major version number? It is a breaking change, after all.

(Feel free to ignore me - nobody asked what I would do!)

Was this page helpful?
0 / 5 - 0 ratings