Update updating-to-new-releases.md #9143
Open
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
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.
I was just updating an existing older project that was built with CRA. Following the changelog to get migration instructions for newer versions of
react-scriptswas a breeze - thanks for this!One thing that did occur to me however, is that since I first created this project the official
cra-templatehas changed quite a bit and now includes things likesrc/setupTests.jsand wrapping the app in<React.StrictMode>. I looked back over the changelog and saw these changes as enhancements upon closer inspection, but I thought a note in the docs to give users a nudge on this would be useful.Might be something here about suggesting updates to
react/react-domas well if possible?