docs: clarify Node.js version requirements for webpack 5 and CLI#8012
Closed
rahul-kr-rai wants to merge 1 commit intowebpack:mainfrom
Closed
docs: clarify Node.js version requirements for webpack 5 and CLI#8012rahul-kr-rai wants to merge 1 commit intowebpack:mainfrom
rahul-kr-rai wants to merge 1 commit intowebpack:mainfrom
Conversation
|
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 resolves inconsistencies in the
Node.jsversion requirements across the documentation. Previously, the Getting Started and Migration Guide stated that webpack 5 requires Node.js>=10.13.0(LTS), while the CLI documentation correctly noted thatwebpack-cli v7requires Node.js>=20.9.0This mismatch created confusion for users setting up webpack.Changes Made
Updated:
src/content/guides/getting-started.mdxUpdated:
src/content/migrate/5.mdxWhat kind of change does this PR introduce?
Fix Inconsistent
Node.jsVersion Requirements in DocumentationBefore:
After:
Did you add tests for your changes?
No,
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