This appears to be caused by reactable/table.jsx::parseChildData()'s mechanism for checking to see if the children are the types it's expecting. child.type returns the function used to create the child component, and RHL will have swapped out the function with a copy of itself. But, since they merely contain the same code (and don't point to the same in-memory instance of the function), JS doesn't see them as being the same function.

I'm unsure that this is something that RHL would be able to fix, though it's probably worth opening a ticket over there, too.

I think there's an easy fix for this on the reactable side, where reactable adds add a "reactable component type" static string variable to each of the reactable components, and checks against that in the switch instead.

@glittershark - If you'd be open to this as an approach, I can try to put together a PR. What do you think?

@glittershark any comments?

I am facing the same issue. Have you guys found any solution?

Still facing similar issue :( with react-hot-loader 4