Clojurians
#cljsrn
<
2016-02-21
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

sherbondy23:02:13

hey all, I’m really interested in a high-level overview of some of the main issues / points of contention at the interface between react native and cljs tooling. I understand that @mneise did some awesome initial work to make it possible to ingest different js module formats, but as far as I can tell react native continues to use its own bespoke packager tool: https://github.com/facebook/react-native/tree/master/packager with odd primitives like @providesModule. Can somebody help fill in the gaps, re: how this impacts cljs tooling and maybe insight into how we can improve the situation?

sherbondy23:02:28

reading through http://cljsrn.org/roadmap.html and trying to grapple with this

sherbondy23:02:23

in some senses it sounds like maybe the best way I can contribute is help with the react native codebase itself towards emitting proper commonjs modules as suggested over a year ago? https://github.com/facebook/react-native/issues/5