Repository navigation
fix: support type: module in server build output - #1701
Merged
Merged
Conversation
commit: |
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.
🔗 Linked issue
Fixes: #1144
❓ Type of change
📚 Description
When a project has
"type": "module"in its rootpackage.json, Node.js treats all.jsfiles as ES modules by default. This causes issues with the server build output, which expects CommonJS semantics.This PR adds a
package.jsonfile with{ "type": "commonjs" }to thedist/serverdirectory during the build process. This ensures that.jsfiles in the server build directory are correctly interpreted as CommonJS modules, regardless of the project's rootpackage.jsonconfiguration.📝 Checklist