@shulc_ @pesterhazy PureScript might also be worth looking into.

Although I suspect the tooling situation might not be as great as in cljs.

@clojurians.net, true, and typescript and flow are also options to consider

they make other tradeoffs

@pesterhazy on an unrelated (but still RN-related) note - did you get around to talking to the re-natal people/guy about getting this in there: https://github.com/pesterhazy/re-natal-husk I used to run into all kinds of nasty transformation failure issues and broken builds with cljs and RN, and this was a life-saver.

Also, thank you for that.

@clojurians.net, I think I never brought it up, if you could raise an issue in the re-natal github, that'd be great

one thing I'm not positive about is how to integrate it with the xcode project in a seamless way

the only way I see it update your XCode project using the XCode UI, or by editing the file

which is not very convenient

I also haven't tried this with Android, so not sure how it fits into the build pipeline there

I'm iOS-only, so no idea either. I'll raise the issue on GitHub.

I'll give the XCode integration some thought as well, at the moment it's a bit messy, yeah. But it works great, no more random build failures at the worst times because some part of the code somehow crossed some invisible complexity threshold making the whole transformation pipeline blow up.

@clojurians.net, same here, this hack just fixed these problems for us

Regarding the integration - maybe re-natal could do what it already does with the enable-source-maps option - just patch the script under node_modules. It's not pretty, but it's easy.

react-native-xcode.sh, that is

I didn't know about enable-source-maps, this might be a good option

the issue I see with that is that rm -rf node_modules && npm install will undo that change

Same issue with enable-source-maps

It's not great, but better.

there's https://github.com/ds300/patch-package

As a workaround until then, I force added the patched react-native-xcode.sh version to my git repo, so I can just check it out after npm install

patch-package might be more foolproof?

it integrates with the "postinstall" setting in package.json

That looks good. I'll check it out and suggest it in the github issue.

👍

Thanks.