Package strategy (get to ESM without breaking other consumers)
Closed this issue · 0 comments
rosskevin commented
I'm interested in hearing from others about package/bundle strategies. Ideally I'd like to publish a UMD, an ES, and ESM so everyone can benefit. Currently I cannot use this library as ESM only because I have at least one dependency that is not ESM. @see microsoft/TypeScript#49388 (comment)
Perhaps we just keep 3.x as ES, and make 4.x as ESM and add the proper exports sindresorhus as has done sindresorhus/meta#15
I welcome thoughts on the issue.