This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-01
Channels
- # aleph (2)
- # beginners (137)
- # boot (4)
- # cider (10)
- # clara (29)
- # cljs-dev (71)
- # cljsrn (7)
- # clojure (105)
- # clojure-bangladesh (1)
- # clojure-france (2)
- # clojure-italy (4)
- # clojure-nl (3)
- # clojure-russia (1)
- # clojure-spec (30)
- # clojure-sweden (5)
- # clojure-uk (71)
- # clojurescript (217)
- # cursive (36)
- # data-science (1)
- # datomic (11)
- # duct (53)
- # fulcro (2)
- # garden (3)
- # jobs (1)
- # lein-figwheel (23)
- # luminus (3)
- # lumo (7)
- # mount (13)
- # off-topic (88)
- # pedestal (3)
- # re-frame (63)
- # reagent (85)
- # remote-jobs (1)
- # ring-swagger (3)
- # shadow-cljs (81)
- # spacemacs (5)
- # tools-deps (16)
- # yada (2)
Hey I've been asking around for having configurable read-cond features in clojurescript. My motivating use-case is doing react - web/native-android/native-ios builds. @dnolen sent me here to gather more information on this. How have y'all been dealing with these kinds of builds? Right now, I'm using separate builds with shared files and tricky classpath management ...
Yep, I'd like to use shadow-cljs for that, since we won't get custom features in regular cljs any time soon.
But the replacement needs to be real smooth, before I can pull it, because my team can't be interrupted by this. So in particular, I need to get it to work together with figwheel for web and native ...