Paweł Gulbinowicz

Hey @szalansun, thanks for opening the issue. I'll look into it in spare time. To me it looks like the app cannot download the bundle from Haul. Usually this is...

> Android works only after "adb -s reverse tcp:8081 tcp:8081" Running this command is necessary even with Metro and it's more of a Android thing than Haul/Metro/React Native. `/debugger-proxy` should...

And the error you've posted is displayed in the terminal when `haul start` is running?? Or where is that coming from?

Ah, I know why it's happening, as usual iOS is behaving differently and for some reason makes a HTTP requests to `/debugger-proxy` here: https://github.com/facebook/react-native/blob/d0871d0a9a373e1d3ac35da46c85c0d0e793116d/React/CoreModules/RCTWebSocketExecutor.mm#L60 whereas Android is constructing correct URL...

There's not easy workaround for that. It needs changes in the haul's server itself, changing how the WebSocket server is created.

@Natteke not every `node_module` package is excluded, some are transpiled but the great majority is not.

@tachtevrenidis When I publish the packages with `lerna` it bumps the versions, but it does not update `peerDependencies` so I have to update them manually and sometimes, the packages are...

The error is caused by dynamic `require` here: https://github.com/realm/realm-js/blob/e53cb3c7b14df7c9d8ca50e03e5c02f95b8f1154/lib/user-methods.js#L26-L28 which from the Webpack point of view cannot be statically analysed hence the error.

As @FredyC said, there's nothing we can do in haul to make it works. This needs to be handled either in Realm codebase itself or make a fork or use...

@FredyC @Krizzu's solution is way cleaner than some production code I have seen 😂