Upgrade React to v18 #2280
Merged
Upgrade React to v18 #2280
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
becca-bailey
force-pushed
the
chore/upgrade-react
branch
from
d577c81 to
e89f71d
Compare
|
@scottrippey I didn't update any lint rules in this PR, but for some reason |
scottrippey
reviewed
Jun 2, 2022
# Conflicts: # package.json # yarn.lock
…ry into chore/upgrade-react
# Conflicts: # package.json # yarn.lock
|
Great! When can we expect a new release on NPM including this fix? |
|
@stur86 Apologies for the delay in getting this released, we have been resolving some build issues on our end, but this should go out before the end of this week. |
|
Thanks, that's fantastic! |
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.
Upgrades React to v18, and updates peer dependencies to work with React 18. (Are there any reasons for us to remove support for v16 right now?)
This also updates a few misc. dependency issues that came up when running
yarn audit.Fixes #2187