Repository navigation
Fix exports map to match actual tsdown output - #8
Merged
Merged
Conversation
The tsdown upgrade to v0.21.7 changed the default ESM output extension from .js to .mjs, but the exports field in package.json was not updated to match. This caused ERR_MODULE_NOT_FOUND when importing the package. Fixes #6
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
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.
Fixes #6
The tsdown upgrade to v0.21.7 changed the default ESM output extension from
.jsto.mjs, but theexportsfield was not updated to match. This causedERR_MODULE_NOT_FOUNDwhen importing the package as ESM.Updates the exports map to point to the actual filenames (
index.mjs,index.cjs,index.d.mts,index.d.cts) and adds proper conditionaltypesentries for both import and require conditions.Scope: package
Visibility: user-facing