There is no real need for async-es package. It ends up complicating async usage downstream especially for projects which emit both cjs and esm. And to complicate things, async-es has a main entry which points to esm (without indicating type: 'module'), so it can't be used for cjs scenarios.
Recommended:
Update the async package.json with:
main pointing to commonjs. (this is only for backwards compatibility.)
module pointing to esm. (this is only for backwards compatibility.)
exports map explicitly listing the valid imports and the cjs/esm/d.ts files to resolve to.
There is no real need for
async-es
package. It ends up complicatingasync
usage downstream especially for projects which emit both cjs and esm. And to complicate things,async-es
has amain
entry which points to esm (without indicatingtype: 'module'
), so it can't be used for cjs scenarios.Recommended:
Update the
async
package.json with:main
pointing to commonjs. (this is only for backwards compatibility.)module
pointing to esm. (this is only for backwards compatibility.)exports
map explicitly listing the valid imports and the cjs/esm/d.ts files to resolve to.