Support esm about node-deep-equal

[ljharb]

It's not actually a best practice, it doesn't solve any problems (although it creates many), and only a very very small number of package authors are inflicting that on the ecosystem right now.

If you're having a specific problem, please file an issue about that; the format of the package should be none of your concern.

[ljharb]

We already do, because ESM can import CJS.

[ljharb]

No, the usual way is to do nothing, since CJS Just Works.

Adding a build step and the dual package hazard isn’t an improvement - CJS is the true universal format.

[Harpush]

We already do, because ESM can import CJS.

I meant in the package json. Currently in angular I get commonjs optimization bailouts warning. I guess providing the mapping in package json can fix that

[ljharb]

Those warnings are incorrect; any purely CJS package is importable from ESM with zero problems. If a bundler is having trouble doing that most basic thing, it's broken, and you should file an issue on it.

[Harpush]

It works just shows a warning. Afaik the usual way is targeting both cjs and mjs using package json exports. Mostly you write esm and compile to cjs too. Is it not possible?

[Harpush]

As far as I know there is the "move to esm" best practice lately. More and more packages support it