[WARNING] findDOMNode is deprecated in StrictMode
See original GitHub issueI’m getting the following warning regarding the react-lazyload
:
Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of VisibilitySensor which is inside StrictMode. Instead, add a ref directly to the element you want to reference.
Is there any idea about when it’ll be resolved? I saw that there was already an issue related to it here but it was closed in 2019.
Issue Analytics
- State:
- Created 3 years ago
- Comments:16
Top Results From Across the Web
Warning: findDOMNode is deprecated in StrictMode ...
The solution to resolve the warning is by using React refs. Refs helps to access DOM nodes or React elements created in the...
Read more >React warning: findDOMNode is deprecated in StrictMode ...
When working with React.js, you will probably come across an annoying warning: Warning: findDOMNode is deprecated in StrictMode.
Read more >React.StrictMode throws warning because of `findDOMNode ...
Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of StyledComponent which is inside StrictMode.
Read more >How do I fix warning findDOMNode is deprecated ... - YouTube
How to fix finddomnode warning with two different method : Warning : findDOMNode is deprecated in StrictMode. findDOMNode was passed an ...
Read more >JavaScript : Warning: findDOMNode is deprecated ... - YouTube
JavaScript : Warning : findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of Transition which is inside StrictMode ...
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
@rafaelcamaram @spenceruns Sorry could not cut a release last week, will release it this weekend
@ryardley @rafaelcamaram @rk2609 @a20070322 this has been fixed and release as verion 2.6.8 in npm, do check and let me know