breaking: Update exports configuration #120
Merged
Conversation
This file contains 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
This is a new(er) style of defining the package's exported files. Gonna keep the `browser` value in there for now since it's officially in the `package.json` documentation, but tbh I'm not entirely sure what might use that.
|
Oh, CI's gonna break on this one. The next PR is going to update the ESLint configuration which will address the issues. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This package is meant to be used in a browser. Browsers use ESM modules. So, we should configure
package.jsonto flag up that this is a module.That required a couple of changes:
"type": "module"topackage.json,eslint.config.jsto use ESM stuff,.mjsfiles to.js,exportsconfig (documentation) inpackage.jsonto define ESM and CommonJS entrypoints