-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Full react 19 support #1866
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
Full react 19 support #1866
Conversation
f3a55d8 to
e1ff44f
Compare
|
Fix for #1858 |
e1ff44f to
5bade1d
Compare
|
Hi can someone please okay this merge! Long awaited feature and fixes. Just 5 mins of maintainer's time. |
Hi, you can use Fixed fork . It seems to me that this PR will not be merged into the master in the near future :) |
|
@bvaughn Please merge this for React 19 support. |
|
@bvaughn let's get this merged! |
5bade1d to
d826874
Compare
|
Updated published as-is to |
|
Worth mentioning somewhere in the changelog that it's introduced the breaking change for WindowScroller render() which now adds an additional |
|
@adubrouski Much thanks for findDOMNode error fix ❤️ |
npm test) all passyarn run prettier).yarn run typecheck).React < 16.3.0 has been removed from peer dependencies for safe React.createRef() usage. I think this would be the right decision. We can release a new version and simply drop support for older versions of React.
ℹ️ Tests still work with findDOMNode, because react version in tests is 17. To remove findDOMNode from tests we need use
@testing-library/react, but it should be in separate PR. We can also access node by ref, but this possibility will be removed in next major react release.📦 Fork published on NPM with full react 19 support (if anyone needs it right now)