-
Notifications
You must be signed in to change notification settings - Fork 47.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read property 'getHostNode' of null #8579
Comments
Please see #8267. Related explanations: #7617 (comment), #4199 (comment). If you’re sure this is not the problem please provide a reproducing example. |
Getting this error in IE. The build application works fine in mozilla and chrome. Moreover, the standalone express server app runs fine too in IE but the built js file using webpack and babel fails to navigate when used inside of a jsp file |
Same here @AjayU |
@AjayU I discovered it was because I was using for(let key of something) { } loops in my code. Apparently this isn't polyfilled properly. Replacing them with .map({})'s worked. Had nothing to do with react-router - it was just that was firing the render call that caused the error to happen. |
this issue occurs for me specifically when using |
Please read this comment: #8579 (comment). I'm locking the issue because further comments will just confuse people googling it. The cause of this error is always another error that happened earlier (but that your code might have swallowed it). |
A small update on this. We just released React 16 beta which shouldn’t emit cryptic errors like this one. Even if the application code swallows an error, React 16 will still print it to the console. It might be too early for you to try React 16 (since ecosystem is still preparing for it), but this error should never occur in the future after you switch to it. |
feature request
What is the current behavior?
Cannot read property 'getHostNode' of null
What is the expected behavior?
An error message that tells me what is wrong so I know what to fix.
"react": "15.3.2"
The text was updated successfully, but these errors were encountered: