`npm.ls()` v4.4.2 changed output, breaking package about find-duplicate-dependencies

[vovacodes]

well this is indeed a very nice scenario of optimization, you almost convinced me to fix this bug and start using this script again :)

[kof]

I have a fix, give me a sec

[kof]

I think I am seeing the same issue, I got printed out many times exact same version for e.g.

  { name: 'warning',
    version: '3.0.0',
    from: '[email protected]',
    path: 'grape-web-client/grape-web/material-ui/react-event-listener' },
  { name: 'warning',
    version: '3.0.0',
    from: '[email protected]',
    path: 'grape-web-client/grape-web/material-ui/react-transition-group' },
  { name: 'warning',
    version: '3.0.0',
    from: '[email protected]',
    path: 'grape-web-client/grape-web/material-ui' },

[vovacodes]

I did not use this tool probably for 2 years already, so there are high chances it is not working with the current version of npm, unfortunately, I don't have much time to fix this now, but would appreciate and accept contributions

[kof]

what do you use instead? maybe there is something else out there? Should be a popular problem …

[vovacodes]

Well I don't use anything at the moment, just rely on NPM and Webpack to dedupe as much as possible, but I agree that monitoring that stuff is quite useful

[kof]

The problem is how do we know that we need to update some dependency in order to avoid loading different versions if a dependency is used across multiple packages? Tools have no choice but to bundle that dependency multiple times. This can't be automated afaik.

[vovacodes]

fixed in [email protected]