Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cryptic error message for findDOMNode of unmounted component
See original GitHub issueAs per https://github.com/facebook/react/issues/2410#issuecomment-115659185: findDOMNode(this) throws for unmounted components, but the error message is too cryptic:
Uncaught Error: Invariant Violation: Component (with keys: getDOMNode,_handleChange,props,context,state,refs,_reactInternalInstance) contains render method but is not mounted in the DOM
Some expert React users honestly thought they had duplicate React or something, so didn’t even bother to check whether the component was mounted. (It wasn’t.)
Issue Analytics
- State:
- Created 8 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
For any who may happen to run across this same error in the future, I recently saw this error which was caused by calling
getDOMNode()on a component that had been unmounted. This was caused by an asynchronous event that then assumed the component was still mounted. AlthoughisMountedis considered an anti-pattern, this is one possible use case that I see it being very convenient for.Got it, thanks. I was just worried we missed some case when adding a warning.