This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-13
Channels
- # admin-announcements (1)
- # beginners (53)
- # boot (355)
- # braid-chat (4)
- # cider (15)
- # cljsjs (3)
- # clojure (88)
- # clojure-austin (1)
- # clojure-new-zealand (4)
- # clojure-russia (46)
- # clojure-uk (7)
- # clojurescript (61)
- # component (2)
- # cursive (3)
- # data-science (5)
- # datomic (6)
- # dirac (49)
- # editors (8)
- # emacs (15)
- # funcool (15)
- # jobs (1)
- # ldnclj (10)
- # melbourne (1)
- # off-topic (14)
- # om (61)
- # om-next (2)
- # onyx (32)
- # re-frame (28)
- # reagent (19)
- # test200 (1)
- # vim (3)
well this would be quite advanced setup, I think you can use figwheel independently as a starting point and then maybe try to integrate them both
it is covered here: https://github.com/bhauman/lein-figwheel/wiki/Using-the-Figwheel-REPL-within-NRepl
maybe you can do what they propose, start nREPL server via lein repl
and then start figwheel from within that nREPL server, and dirac too
I’m not sure, its been a month or two I last saw those nREPL-piggieback-weasel-stuff and I don’t remember details
I usually tend to do a lot of debug printing using cljs-devtools, and sometimes put (js-debugger) around, if I cannot set a breakpoint from UI
btw. you can use cljs-devtools without dirac, that should be your first step if you are new to cljs dev
ehh, i mean I don't agree that having good debugging tools is limited to advanced projects : P
my recommendation: start with cljs-devtools + figwheel, use figwheel’s standard REPL (it is not nREPL)