Export both esm and cjs #42
Conversation
🦋 Changeset detectedLatest commit: a58db56 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| "./utils": { | ||
| "types": "./dist/utils/index.d.ts", | ||
| "require": "./dist/cjs/utils/index.js", | ||
| "module": "./dist/esm/utils/index.js" |
There was a problem hiding this comment.
I saw there were many options we can provide here including import, default, node. How did you choose these two?
There was a problem hiding this comment.
I'm trying to remember where exactly I pulled these from, but there are many sources that don't all give the same keys. https://nodejs.org/api/packages.html#conditional-exports is a good source, and it lines up more with the values you gave. We should probably switch to node and default
|
I tested the published canary package and it works so well. Thanks so much for your help! |
Alternate approach to #39 using
tscinstead ofbabel. This allows consumers of the package to use either CommonJS or ESM.