docs: clarify multiple entry point examples #7739
Merged
+14
−0
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
Simplified multiple entry point examples to avoid confusion around entry keys and file paths. Follow-up to webpack#7328 with updated examples based on @evenstensberg feedback. url: webpack#7328
|
@cengizilhan is attempting to deploy a commit to the OpenJS Foundation Team on Vercel. A member of the Team first needs to authorize it. |
Adds a clarifying comment to explain that entry keys represent logical output paths/names, while values point to source files on disk.
Updates the example to use simple, unique entry key names to better align with documentation expectations.
Member
|
We need to fix linting issue and then we are good! |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
evenstensberg
approved these changes
Jan 9, 2026
Member
evenstensberg
left a comment
evenstensberg
left a comment
There was a problem hiding this comment.
lgtm, thanks Cengiz! ☀️
Contributor
Author
|
Thanks a lot Even! Appreciate the review and the guidance along the way 🙌 @evenstensberg |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Simplified multiple entry point examples to avoid confusion around entry keys and file paths.
Follow-up to #7328 and #7397, with updated examples based on @evenstensberg feedback.
This example is different from the original one. Folder paths in the key and value are used intentionally to demonstrate custom
fromandtopaths.Summary
Clarifies multiple entry point examples by simplifying entry keys and file paths to reduce potential confusion.
What kind of change does this PR introduce?
docs
Did you add tests for your changes?
Not applicable. This PR only updates documentation.
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?
The documentation has already been updated in this PR.