fix: Set file extensions for package entry files #513
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
If the package type is CommonJS all `.js` files will be handled as if they are CommonJS, even if exports is set to module. Same if type is set to ESM, then all `.js` files are handled as if they are modules. So the file extension has to be set to the explicit type. Signed-off-by: Ferdinand Thiessen <rpm@fthiessen.de>
skjnldsv
approved these changes
Mar 16, 2023
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.
If the package type is CommonJS all
.jsfiles will be handled as if they are CommonJS, even if exports is set to module. Same if type is set to ESM, then all.jsfiles are handled as if they are modules. So the file extension has to be set to the explicit type.