Fork me on GitHub
#cljsrn
<
2017-05-15
>
gphilipp11:05:19

@seantempesta do you have an example of using your base navigation namespaces (re-frame here) ?

carocad19:05:19

hey guys, have you ever tried to use hot reloading + cljsbuild for a react native application? I have been using re-natal + figwheel for development but I have some problems with keeping the state of my components. We have been discussing about it here: https://github.com/drapanjanas/re-natal/issues/58. The point is that apparently hot reloading can already covert most of what figwheel is supposed to achieve.

carocad19:05:05

I am currently using re-natal + figwheel + cursive and their integrations leaves lots to be desired. I was wondering if anybody has already tried making cljsbuild work with hot reloading and cursive (or similar) 🙂 ?

pesterhazy19:05:54

@carocad haven't tried it but would be curious

mv20:05:58

@pesterhazy I haven’t tried yet, but outputting to figwheel seems optimal for me

carocad22:05:51

@pesterhazy please correct me if I am wrong (since this seems too easy to be true) but according to my experiments, this two function calls are all that is needed to get a production build or a cljs repl (using vanilla repl - no plugin, leiningen, etc)

(require 'cljs.repl)
(require 'cljs.build.api)
(require 'cljs.repl.node)

(cljs.build.api/build "src"
                      {:output-to "index.android.js"
                       :optimizations :simple})

(cljs.repl/repl (cljs.repl.node/repl-env)
                :watch "src"
                :output-to     "index.android.js"
                :output-dir    "target/android")
                ;:main "env.android.main")