Closed Judahmeek closed 7 years ago
I think (but am not absolutely sure...) that the issue is orphan elements such as https://github.com/YoruNoHikage/redux-devtools-dispatch/blob/27396aa89f4e762f855faffc1ebaf1f8f39cd7b9/src/Dispatcher.js#L195, which were apparently perfectly good back in the day, but (if I'm right) don't provide the element with an owner, even though they have a parent. This causes ReactOwner.addComponentAsRefTo
to throw the error in the comment above.
It would be easier to confirm these suspicions if I could figure out how to transverse the browser's component graph, but till then, I think I'll see if I get the same error on https://github.com/YoruNoHikage/redux-devtools-dispatch/tree/master/examples/counter after I've updated its dependencies and If I can get rid of the error by modifying its source code.
Hey, you're turning on dev tools and sending development-only libraries to the client in production. We need to change this ASAP as this is a no-no
Ah, yes. I meant to address this, but got distracted by everything else. ;-;
use of
dispatcher
,inspector
,filterable-log-monitor
, and/orslider-monitor
(as the default/first child ofdock-monitor
anyway) all result in: