Why not main entry

[dy]

Just a question - I used to create and use many packages with single ‘main’ entry but usable both in browser/node. Now due to this transition to esm we have to generate noise in package.json / dist folder. I thought pika provides graceful solution for web-modules - taking cjs (as I was doing) and compiling that to esm on install, (instead of forcing whole npm to change). That’s obvious there’s a lot of browser legacy cjs modules that aren’t going to transition to esm, like Buffer, tape etc.
Just curious - what’s the strong reason against taking ‘main’ cjs module entry?
Thanks!

[backspaces]

How do you do that?

compiling that to esm on install

Check #62 which discusses cjs -> es6 via rollup and rollup-plugin-commonjs. Is that your approach? Maybe webpack magic?

[FredKSchott]

once Node adds ESM support this will get a lot less noisy, but right now "module" is the only reliably way to detect ESM, which this tool was built specifically for. +1 for following up in #62 about adding CJS backwards compatibility support, which could also help us migrate once Node ESM support goes mainstream.