chore: update react to 16.12.0 #842
Closed
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
|
👋🏼 @godcrampy, thanks for taking the time to open this pull request! While it's a great enhancement for the existing site, I believe that most of these issues will be solved with the migration to Gatsby (#896). That PR will be moved to its own branch and then cleaned up with additional PRs. If these issues are still present, then it would be best to tackle them there. So I'm going to close this for now, but if you have any concerns or think I'm mistaken - let me know! |
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.
Changes Introduced:
react-dom-factoriesasReact.DOM.<element>is deprecated in react16+keywarnings in element lists16.12.0Closes #776