npm Community Forum (Archive)

The npm community forum has been discontinued.

To discuss usage of npm, visit the GitHub Support Community.

`npm ddp` results in "error with npm itself"

What I Wanted to Do

Dedupe my dependencies.

What Happened Instead

I ran npm ddp, and got an error telling me to report it here.

Reproduction Steps

  1. npm i
  2. npm ddp


Certain details have to be censored, as I am not at liberty to divulge them. Censored information has been replaced with the word “CENSORED”.

$ npm ddp
(node:37100) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '0' of undefined
    at rmStuff (C:\Users\CENSORED\AppData\Roaming\nvm\v10.11.0\node_modules\npm\lib\unbuild.js:61:24)
    at Array.<anonymous> (C:\Users\CENSORED\AppData\Roaming\nvm\v10.11.0\node_modules\npm\node_modules\slide\lib\bind-actor.js:15:8)
    at LOOP (C:\Users\CENSORED\AppData\Roaming\nvm\v10.11.0\node_modules\npm\node_modules\slide\lib\chain.js:15:14)
    at C:\Users\CENSORED\AppData\Roaming\nvm\v10.11.0\node_modules\npm\node_modules\slide\lib\chain.js:18:7
(node:37100) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:37100) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <>

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\CENSORED\AppData\Roaming\npm-cache\_logs\2018-10-09T16_57_08_459Z-debug.log

Platform Info

$ npm --versions
{ 'CENSORED': '1.0.0',
  npm: '6.4.1',
  ares: '1.14.0',
  cldr: '33.1',
  http_parser: '2.8.0',
  icu: '62.1',
  modules: '64',
  napi: '3',
  nghttp2: '1.33.0',
  node: '10.11.0',
  openssl: '1.1.0i',
  tz: '2018e',
  unicode: '11.0',
  uv: '1.23.0',
  v8: '',
  zlib: '1.2.11' }

$ node -p process.platform

It looks like someone else may have already reported this bug.

Closing as dupe, then