This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-21
Channels
- # aleph (5)
- # aws (3)
- # bangalore-clj (1)
- # beginners (8)
- # boot (198)
- # cider (4)
- # cljsjs (5)
- # cljsrn (2)
- # clojure (14)
- # clojure-argentina (1)
- # clojure-dusseldorf (8)
- # clojure-greece (29)
- # clojure-italy (10)
- # clojure-japan (1)
- # clojure-poland (4)
- # clojure-russia (8)
- # clojure-spec (51)
- # clojure-uk (8)
- # clojurescript (97)
- # cursive (4)
- # datomic (6)
- # emacs (2)
- # events (2)
- # figwheel (3)
- # hoplon (32)
- # lein-figwheel (5)
- # leiningen (1)
- # luminus (2)
- # off-topic (29)
- # om (109)
- # other-languages (38)
- # proton (3)
- # re-frame (3)
- # ring (1)
- # slack-help (10)
- # testing (1)
- # uncomplicate (1)
- # untangled (21)
- # vim (10)
- # yada (11)
@bhauman I have a couple of questions while working on boot-figwheel
. I was planning to disable the auto watcher in the system map somehow and use watch
in boot with the build once feature.
The question is, will I still keep the HUD+nice messages functionality or build once just compiles the javascript without sending anything on the websocket?
@richiardiandrea you will have to translate boot watch event data into the figwheel server event that the figwheel autowatcher calls
@richiardiandrea: If you can get figwheel working as well in boot as it does with lein I'll buy you a drink at the Conj 🙂 It's the last thing boot is missing that is preventing me from trying it out.
@bhauman well I was thinking of using build once in order to avoid the watcher machinery...so build once does not have the nice error messages I gather...
@shaun-mahood lol, boot-cljs
+ reload
works well but is also slower then figwheel when compiling I noticed
@richiardiandrea: Figwheel or nothing! 🙂