Closed carocad closed 5 years ago
This is ClojureScript issue
@bhauman sorry for the poorly explained issue. You are right that the issue is from Clojurescript, however, the issue that I wanted to point out is that it is not possible to know what went wrong on the repl since figwheel doesnt show it.
The feedback simply says message from client couldnt be read
, which of course could mean a lot of things.
Would it be possible to improve that? I would be willing to help if possible :)
I think this is fixed in figwheel-main. I'm suggesting that folks move over as the improvements are many.
When I say fixed I mean that the message is a tad clearer.
I am using the figwheel bridge together with the Expo template for a react native app.
I just migrated to node.js compilation target and started using js interop for requiring modules through the namespace form.
Everything seems to work fine for "standard" requires (those with simple names like react, react-native, expo) but if I try something like below then figwheel complains it cannot read it.