4 ms·

However note that ESM in Node comes with drawbacks that prevent end-users from relying them in various situations. Those will be mostly solved once loaders beco

However note that ESM in Node comes with drawbacks that prevent end-users from relying them in various situations. Those will be mostly solved once loaders become stable, but until then it's still advised to ship packages as both CJS and ESM.

rattray 5y ago
How do you do both?
- inglor 5y ago
  It's very easy to re-export ESM (import) as CJS (require) and vice-versa. The main issue is that ESM by default For example to use `require` inside ESModules you would do: ```mjs import { createRequire } from 'module'; const require = createRequire(import.meta.url); require('./whatever-in-cjs'); ``` There is a reason this isn't "by default" though since ESM doesn't "silently" interop with CJS to not make writing universal code harder.
- arcatek 5y ago
  Usually you setup a transpiler to target both. For example, my packages are bundled with rollup towards both cjs & esm: https://github.com/arcanis/clipanion/blob/master/rollup.config.js#L6-L17 https://github.com/arcanis/clipanion/blob/master/rollup.conf...
  - rattray 5y ago
    Helpful, thank you!