feat: publish ESM bundle #302
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a bundle step to add mjs files to the dist folder, so that this project can be used natively as ESM without requiring a bundle-step on the consumer's end.
This isn't the same as the browser output since that just makes the default export available as a global variable on window.
The reason why publishing as ESM (as opposed to browser global var) is preferred is because then it can be used in an isomorphic way in both Node and the Browser.
Even better would be for this package to be written in native ESM but maybe that's a contribution for another day, also let me know if you'd be open to it.