This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-30
Channels
- # beginners (32)
- # boot (15)
- # cljs-dev (200)
- # cljsjs (1)
- # cljsrn (18)
- # clojure (4)
- # clojure-austin (2)
- # clojure-spec (6)
- # clojure-uk (8)
- # clojurescript (69)
- # cloverage (1)
- # cursive (12)
- # datomic (1)
- # dirac (37)
- # emacs (1)
- # hoplon (38)
- # off-topic (3)
- # om (19)
- # om-next (1)
- # onyx (4)
- # parinfer (2)
- # perun (27)
- # protorepl (4)
- # re-frame (5)
- # rum (9)
- # spacemacs (8)
- # untangled (2)
Soooo.... I assume someone on here has figured out the right tweaks to/on top of the clojure layer to hook into figwheel? :-)
@gowder what exactly are you trying to do? Do you want to run figwheel when “jacking-in”? Do you want two repls - CLJ and CLJS?
@ag: I'd be happy with just an option to jack into a running figwheel repl as an alternative to the normal clj repl
@gowder you can you cider-connect to connect to a running repl, but you’d lose some clj-refactor functionality
however if you have a script (similar to a sass-script) described in figwheel’s wiki, you can do something like this:
((nil . ((cider-lein-parameters . "do clean, repl :headless")
(cider-cljs-lein-repl . "(start) (repl)"))))
if you put this into dir-locals.el of your project - whenever you run cider-jack-in-clojurescript
it will run the second thing and you’d have 2 independent repl bufers - one for Clojure. another for Clojurescript