-
Notifications
You must be signed in to change notification settings - Fork 61
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
Invariant Violation on forceUpdate #46
Comments
The reason for this behavior is that LiveReactload tries to reload Unfortunately I haven't found any silver bullet yet, but instead you can use the hack described in #43 gist. |
Thanks for responding. Yes, I saw the gist and the issue you linked too. What hack are you referring to specifically? Is it line 35 |
Nope. The hack is to create and run routes inside This however has a negative side effect: changes to your route definitions are not hot-reloaded. |
I have done more diagnosing and found the issue. The error I experienced seems to occur whenever I cause a reload while I'm "in a Route." As an example from your gist, if I follow a taco Route and then change some code, I get the above mentioned error (though that particular example will complain about The window.onload solution does not resolve the error. |
Aah I get it... |
+1 |
Could you check if this problem is solved in the brand new |
Closing this one since there are no new replies since Sep 18. |
I am setting up a project with livereactload and react-router. Initially the project loads correctly (livereactload starts up without problems, the page renders without errors, etc.).
The first change I make is reloaded correctly in the browser, but I also get the following message in the browser:
Any subsequent changes to code are not successfully made in the browser but I get repeats of the above error.
Any suggestions?
The text was updated successfully, but these errors were encountered: