docs(#7717): clarify Webpack 5 minimum Node.js version wording#7718
Merged
evenstensberg merged 1 commit intowebpack:mainfrom Nov 29, 2025
Merged
Conversation
|
@KhushiYadav-26 is attempting to deploy a commit to the OpenJS Foundation Team on Vercel. A member of the Team first needs to authorize it. |
|
|
|
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
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.
Summary
This PR updates the Webpack 5 documentation to clarify the minimum required Node.js version.
The previous wording "Webpack 5 runs on Node.js version 10.13.0+" could be confusing for new users.
This change makes it explicit that Node.js version 10.13.0 or later is required.
What kind of change does this PR introduce?
Documentation clarification
Did you add tests for your changes?
No, this PR only affects documentation.
Does this PR introduce a breaking change?
No, this change does not affect functionality or break existing code.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
The clarification is already included in the documentation; no further changes are needed.