Release fix for StrictMode warnings
See original GitHub issueWould it be possible to release a new version? The latest unreleased commit seems to include fixes for React StrictMode warnings about not using findDOMNode
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
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 >Fix <StrictMode> warnings #897 - reduxjs/react-redux - GitHub
Is it possible to replace componentWillReceiveProps because is deprecated to remove React 16+ warning.
Read more >Using strict mode in React 18: A guide to its new behaviors
In this article, you'll learn about Strict Mode, its various features, and how the v18 release has improved its API.
Read more >StrictMode - Android Developers
StrictMode is a developer tool which detects things you might be doing by accident and ... But don't feel compelled to fix everything...
Read more >How to Enable React Strict Mode - Kent C. Dodds
Remember, your code will continue to work whether you're using strict mode and fixing the warnings or not. ... You can use <React.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
Hi @ameerthehacker! Have you been able to look at this?
@stigkj this has been in my backlog for a long time and I’m super sorry as It was a busy time, will do that this week for sure