This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-03
Channels
- # admin-announcements (7)
- # beginners (30)
- # boot (181)
- # cbus (1)
- # cider (55)
- # cljs-dev (8)
- # clojure (104)
- # clojure-dev (3)
- # clojure-japan (1)
- # clojure-russia (70)
- # clojurescript (139)
- # core-logic (4)
- # cursive (23)
- # datomic (25)
- # devcards (10)
- # events (11)
- # funcool (1)
- # hoplon (39)
- # jobs (10)
- # ldnclj (19)
- # lein-figwheel (21)
- # off-topic (4)
- # om (174)
- # onyx (46)
- # re-frame (25)
- # reagent (3)
- # yada (7)
the way I was previously getting a figwheel repl going in Emacs doesn’t seem to work. I don’t know if it’s version related
(but I am using 0.5.0-SNAPSHOTfor figwheel and figwheel-sidecar)
@bhauman what’s the significance of using -m clojure.main
? I ask because when I start the repl that way, then follow the system steps in the sidecar readme, it all works. When I start it via cider-jack-in
with the system stuff in my user.clj
as you suggested, it starts Figwheel but it won’t connect on browser load, and so doesn’t get the prompt. Let me know if I should just chill & wait on the coming push
@jeremyraines: cider-jack-in calls lein repl
these are very different environments. I'm still working on fixing the (cljs-repl) start
thanks
@jeremyraines: I just fixed the (use 'figwheel-sidecar.repl-api) (cljs-repl)
use case make sure you do a lein clean
before starting figwheel
sweet, will try it out now
not working for me
still get the message about the system not being started
(I assume I was supposed to comment out the stuff I had put in user.clj)
is there any reason lein-clean
would not work as expected?
lein clean
i mean
@bhauman: there are a few small closing bracket typos in https://github.com/bhauman/lein-figwheel/tree/master/sidecar - do you prefer a pull request or shall i mention them here? (i've been staring at my screen waiting for sys/build-switching-cljs-repl
to finish for minutes before realising the command wasn't complete)
something else: i'm trying to get remote figwheel on node.js to work (writing code on my mac, while seeing it run on an intel edison) using :websocket-host
. the websocket connection is established and an edit triggers a reload on the edison, but it can't find the generated file /home/root/dev/fmp/out/5817F9F.js (since it was generated on the mac). is there an option to have the compiled code sent over websockets as well, or is there another way to get this to work?