Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support React 17 (Fixes #751) #755

Closed
wants to merge 3 commits into from
Closed

Support React 17 (Fixes #751) #755

wants to merge 3 commits into from

Conversation

alexandernst
Copy link
Contributor

Checklist

  • The code has been run through pretty yarn run pretty
  • The tests pass on CircleCI
  • You have referenced the issue(s) or other PR(s) this fixes/relates-to
  • The PR Template has been filled out (see below)
  • Had a beer/coffee because you are awesome

What?

Upgrade to React 17

Why?

Because it will provide better support in the long term.

How?

By upgrading all libraries that haven't been upgraded to React 17 (bugging their creators), then updating this library.

@alexandernst
Copy link
Contributor Author

This fixes #751

@alexandernst alexandernst changed the title [WIP] Support React 17 (Fixes #751) Support React 17 (Fixes #751) Oct 29, 2020
@dylanvorster
Copy link
Member

Feels like we should just go all in with 17, and not even worry about 16, thoughts?

@alexandernst
Copy link
Contributor Author

It doesn't hurt to leave React 16, at least for the moment. Even if 16 and 17 are completely compatible, a lot of projects haven't updated yet their peer dependencies, which means that if you leave only React 17, people will get warnings as the one I added in #751. It won't break anything, but it will show warnings when running "yarn install".

@alexandernst
Copy link
Contributor Author

@dylanvorster Is there anything else I should add to this?

@dylanvorster
Copy link
Member

Upgraded all the deps, its now in master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants