fix: package exports and ESM support #167
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.
Description
type: module
topackage.json
enforcing the project to use node's native ESM format for all files.TypeScript team has a strong stand that they won't rewrite imports to be compatible with node. So the only way to get valid node compatible ESM output (which requires file extensions in imports) is to write valid ESM in the project. The combination of
type: module
in package andmodule: NodeNext
in tsconfig enforces this format.Valid ESM in -> Valid ESM out
Checklist