This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-05
Channels
- # admin-announcements (3)
- # architecture (1)
- # beginners (16)
- # boot (14)
- # cljsrn (205)
- # clojars (4)
- # clojure (100)
- # clojure-austin (2)
- # clojure-india (1)
- # clojure-poland (7)
- # clojure-russia (95)
- # clojure-spec (25)
- # clojure-uk (127)
- # clojurescript (32)
- # core-async (7)
- # cursive (2)
- # datascript (4)
- # datomic (3)
- # editors-rus (1)
- # emacs (8)
- # events (10)
- # funcool (5)
- # gorilla (2)
- # hoplon (6)
- # jobs (1)
- # lein-figwheel (7)
- # leiningen (2)
- # luminus (11)
- # om (7)
- # onyx (119)
- # other-languages (31)
- # proto-repl (1)
- # proton (37)
- # protorepl (3)
- # re-frame (60)
- # reagent (8)
- # spacemacs (9)
- # specter (21)
- # spirituality-ethics (2)
- # yada (10)
I’ve had some trouble with every clojurescript setup I’ve tried with Spacemacs and live reloading. What do you all do in terms of getting nREPL working with a live reloader? (With either of boot or lein)
@porglezomp, do you mean something like Figwheel?
@akiva: Yeah, like Figwheel, but Figwheel and nREPL is an “advanced configuration” that broke on me last time I tried to set it up. Right now I’m using the boot reloader, but that also seems to break after a while, and start claiming that variables are undefined right before successfully evaluating them.
Ah, I’ve been using Figwheel successfully for a long time through Leiningen. It’s pretty solid now.
I don’t use nREPL with it, though. I keep a separate REPL going for connecting to Spacemacs. I just keep Figwheel humming for CLJS stuff only.
I struggled to get a good figwheel + in-editor cljs repl going (> 1 yr ago, things may have improved, and actually that was with vim+fireplace), and eventually (based on a recommendation from the figwheel author) starting treating the browser as my REPL, and I've been pretty happy with that ever since.