This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-28
Channels
- # beginners (98)
- # cider (11)
- # clj-kondo (18)
- # cljsrn (4)
- # clojure (31)
- # clojure-uk (5)
- # clojuredesign-podcast (1)
- # clojurescript (18)
- # cursive (11)
- # dirac (5)
- # emacs (1)
- # figwheel-main (6)
- # fulcro (13)
- # off-topic (3)
- # pathom (3)
- # reagent (3)
- # rewrite-clj (1)
- # shadow-cljs (2)
- # tools-deps (19)
- # vim (2)
I've made a few attempts at getting Dirac working with shadow-cljs, mostly failing. Got a bit further than https://github.com/thheller/shadow-cljs/issues/167 by using a separate nREPL (i.e. not the shadow-cljs nREPL), but then am I correct in thinking I need to hook that up to the shadow-cljs compiler to get correct reloading etc?
@superstructor I’m afraid this would be very hard task. You would need to run shadow-cljs compiler in the same JVM as nREPL server with dirac middleware and then use shadow-cljs compiler env as input for cljs compilation in dirac middleware. I’ve done something like this with figwheel: https://github.com/binaryage/dirac/blob/master/docs/about-repls.md#dirac--figwheel https://github.com/binaryage/dirac/blob/master/src/nrepl/dirac/nrepl/figwheel.clj
figwheel-sidecar.repl-api
was easy enough to give me api to enumerate all compiler states and access to cljs compiler envs: