Because inspectHooksOfFiber reads values from the Fiber, DevTools needs logic to determine which is the current fiber. (It general tries to abstract over this with the concept of an "opaque node" which could either be the current or alternate.)

I believe I can hack this in by comparing data.state to the opaque node's memoizedState, but it's kind of leaky and gross. Maybe we can clean this up later.

Can we make currentDispatcher an optional last argument which defaults to looking up in require('react') but allows you to override it from DevTools? That way anyone using this tool bundled with their app such as if you install it from npm, it just works out of the box without having to drill into the secret object? But you still have the option to.

Yes, I can make this change. It seems a bit weird to me though because if you forget to inject a value in the DevTools use case, you'll be reading/writing from the wrong dispatcher ref. I see the usefulness for this though in cases like you describe.

Edit Although I guess in this case, React would throw an error right away so at least it wouldn't be a silent failure. Should we catch and re-throw a more meaningful error in this case?

Okay. Back to you @sebmarkbage

Generated by 🚫 dangerJS