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.
findDOMNode is deprecatedfindDOMNode is deprecated in StrictMode 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 not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in React
- React must be in scope ReferenceError: React is not defined / 'React' must be in scope when using JSX
- No QueryClient set Error: No QueryClient set, use QueryClientProvider to set one
- Functions cannot be passed Error: Functions cannot be passed directly to Client Components unless you explicitly expose it by marking it with "use server".
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 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.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 14 Oct 2026