3 ms·

Oh, that's awful. It depends on ansi-wrap (another pretty much 1-liner package) with 2.6M weekly downloads. Is there a site or code snippet where I can see wh

by tyingq 5y ago

Oh, that's awful. It depends on ansi-wrap (another pretty much 1-liner package) with 2.6M weekly downloads. Is there a site or code snippet where I can see which of the popular dependants was fooled into using this crap and is driving most of the downloads?

phist_mcgee 5y ago
`npm ls <package_name>` or `yarn why <package_name>` is a good start for figuring out how a package ended up in your node_modules
- tyingq 5y ago
  Sure, I was looking for the opposite...which popular node package is pulling in ansi-wrap.
  - jcuenod 5y ago
    https://www.npmjs.com/browse/depended/ansi-wrap https://www.npmjs.com/browse/depended/ansi-wrap
    - tyingq 5y ago
      Close, though sorted by popularity/downloads is really what I wanted...how to find where all the downloads are coming from.
    - jcuenod 5y ago
      I think that is sorted. If you go to the first result for `ansi-wrap` -> `ansi-gray` -> https://www.npmjs.com/package/fancy-log https://www.npmjs.com/package/fancy-log ("Log things, prefixed with a timestamp." by other creators: 2 398 259 weekly downloads)
      - tyingq 5y ago
        Ah, yep...thanks. So we know where this particular bit of madness could be fixed.