docs: update output configuration examples to ESM #7740
Conversation
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
|
@Mohit-singh-Developer is attempting to deploy a commit to the OpenJS Foundation Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
This PR updates several generic webpack configuration examples in
src/content/configuration/output.mdx from CommonJS (module.exports)
to modern ESM syntax (export default).
The goal is to keep the documentation aligned with how most users write
webpack configuration files.
Only simple, configuration examples were updated.
Examples that intentionally shows CommonJS output
behavior were left unchanged.
What kind of change does this PR introduce?
Did you add tests for your changes?
No. This PR only updates documentation examples and does not affect
runtime code or logic.
Does this PR introduce a breaking change?
No. These are documentation-only changes and do not alter webpack
behavior or public APIs.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
The documentation has already been updated in this PR by modernizing
generic output configuration examples to ESM where appropriate.