docs(target): fix contradiction about multiple targets support#8275
Merged
Conversation
The concepts page claimed webpack does not support multiple strings in target, contradicting the configuration page. webpack 5 supports an array of targets; only a universal web+node target is unsupported for now.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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
The concepts page claimed webpack does not support multiple strings in
target, contradicting the configuration page which documentstarget: ["web", "es5"]. This aligns both pages: webpack 5 supports an array of targets (the common subset of features is used), including combiningwebandnodeto build universal code. Adds atarget: ["web", "node"]example on both pages. Fixes #8265.What kind of change does this PR introduce?
docs
Did you add tests for your changes?
n/a — documentation-only change.
Does this PR introduce a breaking change?
No.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
n/a
Use of AI
AI (Claude Code) was used to locate the contradicting passages and draft the corrected wording and examples; the changes were reviewed for accuracy against webpack 5 behavior.