Error AtlasError Documentation and Resolution
Back to searchMore npm errors

npm

npm cb() never called when using shrinkwrapped dependencies

cb() never called!

npm can fail with cb() never called due to a subtle race condition involving shrinkwrapped dependencies, especially on older npm versions.

cb() never called!installation

Observed message

cb() never called!

Why it happens

  • A race condition affects installs using shrinkwrapped dependencies.
  • The active npm version is old enough to still contain the bug.
  • npm-shrinkwrap.json triggers the failing resolution path.

How to fix it

  1. Update npm to a newer version.
  2. Temporarily move npm-shrinkwrap.json out of the way and retry the install if needed.
  3. Re-run the install after confirming the active npm version changed.

Official reference

npm Docs: Common errors

Related errors

ENOGIT / not found: gitnpm could not find gitENOSPCnpm could not write because the drive is full or not writableEACCES permissions errornpm EACCES permissions error during global installError: ENOENT, stat C:\Users\<user>\AppData\Roaming\npmnpm ENOENT for AppData Roaming npm directory on Windows

Explore more

npmBrowse more npm errorsinstallationBrowse more installation errors
npm cb() never called!: causes and fixes | Error Atlas