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 #4721
Comments
+1 too lazy to pass to final form yet, and i rather stop doing npm i --force all the time :p |
What is the solution for now? npm i --force? |
I do that in docker to fix the issue. |
Installing package is one thing, it's possible with a yarn or using flags --force / --legacy-peer-deps with a npm. Bigger problem is that package is not fixed to accept fixes that made for React 16.8 - 17. It's time to drop deprecated lifecycle methods. Editing package requirement doesn't fix the problem. |
at the end i made the migration to react-final-form that is way much better. Its a little work but it's quite compatible and the whole everything seems faster. |
The PR with partial rewrite of UNSAFE methods need help to rewrite 4 remaining methods |
This issue has been resolved with v8.3.10 |
Support React 17
React v17 has been released and is stable with no major breaking changes from v16.
Problem
Our project is currently stuck at React v16 because this package's peer dependency to react is locked to
^16.4.2
. Blocking us from upgrading out of v16.Expected behavior
I'm suggesting we add v17 to the peer dependencies:
react: >=16.4.2 || ~17.0
.So that we are able to move our projects to React 17
The text was updated successfully, but these errors were encountered: