Warning in StrictMode
See original GitHub issueWarning: findDOMNode is deprecated in StrictMode. ... Instead, add a ref directly to the element you want to reference.
Would be a version with ref support?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Strict Mode - React
StrictMode currently helps with: Identifying components with unsafe lifecycles; Warning about legacy string ref API usage; Warning about deprecated findDOMNode ...
Read more >How can I solve strict mode warning without removing strict ...
In StrictMode we can see the potential warnings. Warnings tell us to make a change in code to improve performance. Isn't it? But,...
Read more >What is StrictMode in React? - KnowledgeHut
It's exclusively used in Development Mode to warn about legacy refs. To make it simpler to notice unanticipated side effects implemented in ...
Read more >How to Enable React Strict Mode - Kent C. Dodds
Rendering your app in React.StrictMode will warn you when a component is using a suboptimal method or API and it will help you...
Read more >Warning on React strictmode | General Discussion | Wijmo 5
Warning on React strictmode ... If we use React strict mode with wijmo, warnings will appear. Do you plan to change findDOMNode to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s not working for me unfortunately. I’m using v4.2.1
However, I hate all these warnings so in version 4.1.0 I added
targetDomEl
property 😃The library doesn’t use the
findDOMNode
method when you pass this property.For example:
Before (findDOMNode is used)
After (without findDOMNode)
Yes, you have to add an extra prop, but this should remove the annoying warning from a console.