Notifications with strict mode (findDOMNode warning)
See original GitHub issueRelates to https://github.com/mantinedev/mantine/issues/93 but in @mantine/notifications@3.1.4 (latest Safari).
notifications.showNotification({
message: `Success!`,
});
Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of Transition which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://reactjs.org/link/strict-mode-find-node
Issue Analytics
- State:
- Created 2 years ago
- Reactions:8
- Comments:13 (6 by maintainers)
Top Results From Across the Web
Warning: findDOMNode is deprecated in StrictMode ...
1. Just a note: the warning seems to disappear when you run the built version. · 3 · 1 · This solution is...
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 >React warning: findDOMNode is deprecated in StrictMode ...
The Problem When working with React.js, you will probably come across an annoying warning: Warning: findDOMNode is deprecated in StrictMode.
Read more >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 >findDOMNode is deprecated in StrictMode, react-redux-notify ...
This is an error probably from a library you are using to say that the ReactDOM.findDOMNode function is now deprecated but it still...
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 Free
Top 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
The issue is fixed, the fix will be released with 4.0 release
End of march - mid april