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
findDOMNode will be deprecated #209
Comments
Maybe we should implement some ref pass through technique to bypass this issue? The DOM node should be accessed anyway though. |
@ameerthehacker Any news on when #242 will make it into an npm release? The build files in 2.6.2 still have the |
bump It would be great if we could get a release with this fix! |
I do believe that it's an important fix that needs to be accomplished. These warn are being very annoying. |
@rafaelcamaram I totally understand it, the fix has been in beta for few weeks now already and I will release it tomorrow |
Starting from React 16.6 it is deprecated in StrictMode and it will be deprecated from React in the future. Here is some more information about this.
The docs state the following:
The warning in StrictMode:
The text was updated successfully, but these errors were encountered: