Skip to content
This repository was archived by the owner on Aug 11, 2022. It is now read-only.
This repository was archived by the owner on Aug 11, 2022. It is now read-only.

cb is not a function error #13457

@adrian-nitu-92

Description

@adrian-nitu-92

I'm opening this issue because:

  • npm is crashing.
  • npm is producing an incorrect install.
  • npm is doing something I don't understand.
  • Other (see below for feature requests):

What's going wrong?

Running the latest node produces on a npm install the following error, several times:

npm ERR! cb is not a function
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>
npm ERR! Linux 4.2.0-27-generic
npm ERR! argv "/home/lp-jenkins/workspace/NovaNodeJS_nightly/builds/2016-07-22_11-47-16/node/install/usr/local/bin/node" "/home/lp-jenkins/workspace/NovaNodeJS_nightly/builds/latest/node/install/usr/local/bin/npm" "install"
npm ERR! node v7.0.0-pre
npm ERR! npm  v3.10.3

How can the CLI team reproduce the problem?

supporting information:

  • npm -v prints: 3.10.3
  • node -v prints: v7.0.0-pre
  • npm config get registry prints:
  • Windows, OS X, or Linux?:
  • Network issues:
    • Geographic location where npm was run:
    • I use a proxy to connect to the npm registry.
    • I use a proxy to connect to the web.
    • I use a proxy when downloading Git repos.
    • I access the npm registry via a VPN
    • I don't use a proxy, but have limited or unreliable internet access.
  • Container:
    • I develop using Vagrant on Windows.
    • I develop using Vagrant on OS X or Linux.
    • I develop / deploy using Docker.
    • I deploy to a PaaS (Triton, Heroku).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions