Repository navigation
Correct outdated contributor documentation - #8734
Draft
aurorascharff wants to merge 4 commits into
Draft
aurorascharff wants to merge 4 commits into
aurorascharff wants to merge 4 commits into
Conversation
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
aurorascharff
changed the title
This branch was successfully deployed
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
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.
Correct the contributor docs' outdated Node requirement, dependency version, content/cache paths, translation and support links, and missing style-guide reference. Add the fork remote required by the existing clone/pull/push commands and describe what
check-allactually does.Remove the obsolete claim that ES6 is new. Replace the example that incorrectly treats standardized class fields as experimental with an experimental
doexpression and a standardifstatement. Preserve the existing don't/do example structure and writing conventions.The package's Node engine range now matches Next.js 15.1.12. This PR does not change CI runtimes.
Validation:
yarn ci-checkpassed on the existing Node 20.20.2 runtime. Tested the documented Git workflow using temporary local repositories. Verified that the negative example requires experimental parser support and that the standard example renders both states correctly. Checked the proposal's status against TC39's current proposal list, plus the Node engine range, original CI workflows, referenced paths, and whitespace.