Update react version in package.json #28
Open
Conversation
This file contains 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
The previous version notation was accurate before react team has released the react@17 and react-dom@17 Now we know these versions contain almost no breaking change at all! So I guess it's safe to kick the can down the line till a future @18 version 😅
|
On the same note, why you have react in both |
|
I want this changes too! @tarunmangukiya |
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.
The previous version notation was accurate before react team has released the react@17 and react-dom@17
Now we know these versions contain almost no breaking change at all!
So I guess it's safe to kick the can down the line till a future react@18 version 😅
We have issues with the current version since we upgraded to new react-scripts with react@17 and we had to work around it by using the resolutions field in package.json
But I think that wouldn't be that easy to solve for guys that are using npm.