Warning: findDOMNode is deprecated and will be removed in the next major release.
A component (often an old library like react-transition-group v1, react-draggable) uses findDOMNode, which StrictMode flags and React 19 removes.
Seen on:
React
Meaning
findDOMNode breaks component abstraction. Libraries offering a nodeRef prop avoid it.
Common causes
- Old libraries using findDOMNode
- Class components using findDOMNode
⚡ Quick fix
- Upgrade the library
- Pass nodeRef where supported (react-transition-group, react-draggable)
- Use refs directly
Detailed fix by platform
React
<CSSTransition nodeRef={nodeRef} in={show} timeout={200}><div ref={nodeRef} /></CSSTransition>
How to diagnose
- Library — Which component in the stack?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026