fredkschott / analyze-npm Goto Github PK

Reading the pika website it seems packages are filtered by the module key which is an (unofficial) convention. This mean dual-mode packages are not included in pika right? It would be good to include these.

Hi,

I thought it might be insightful to parse npm run scripts in a package.json to figure out the most used tools.

If that is do-able, it would make for some beautiful data.

Neat site!

Not sure if this is the best place to request this, but it would also be extremely helpful for TypeScript developers to be able to search for npm packages with a typings property in their package.json. This indicates that the package includes type declarations.

It would be great to learn more about these packages, and the state of ESM on npm overall.

Ideas for data to collect:

• most common method of supporting both esm and cjs? (CJS sources? ESM sources? two outputs? a polyfill? etc.)
• ESM packages that don't specify "module"?
• Others?

A followup to:

• https://twitter.com/43081j/status/1069982523093123072
• https://twitter.com/AvivRubys/status/1070071294618730498

Now when Node has support for modules, some packages started to care about ESM version.

It turns out the "module" field isn't always the best solution, because of webpack.
See for example this PR where it was decided to remove it: markedjs/marked#1571 (comment)

Also I found this article relevant: https://2ality.com/2019/10/hybrid-npm-packages.html

@FredKSchott would you consider adding more ways to discover ESM packages?

This is important for me as a library maintainer: I was hoping to get @pika/web and CDN support when upgrading to ESM version of dependency, but so far I'm out of luck.