Change package type to module (ESM) #395
Merged
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.
🛠 Summary of changes
Changes package to use ES Modules as the default module type.
This avoids the need for using
.mjs
extensions, and may eventually enable future revisions avoiding a build step altogether, shipping the original source files without Babel preprocessing.As mentioned in the included CHANGELOG, this should not have an impact on downstream projects, possible thanks to support for
package.json
exports
allowing a CommonJS to resolve therequire
-based distribution.📜 Testing Plan
Verify tests pass:
Observe that built output via
npm run build:pkg
includes expectedrequire
orimport
semantics inbuild/cjs
andbuild/esm
files respectively.