This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-29
Channels
- # ai (2)
- # beginners (12)
- # bitcoin (1)
- # boot (41)
- # chestnut (5)
- # cider (9)
- # clara (24)
- # cljs-dev (11)
- # clojure (107)
- # clojure-dev (2)
- # clojure-italy (4)
- # clojure-nl (4)
- # clojure-russia (10)
- # clojure-spec (19)
- # clojure-uk (71)
- # clojurescript (121)
- # cursive (3)
- # data-science (7)
- # datacrypt (1)
- # datomic (72)
- # docs (7)
- # duct (2)
- # emacs (3)
- # ethereum (1)
- # figwheel (1)
- # fulcro (58)
- # graphql (16)
- # hoplon (9)
- # jobs (2)
- # jobs-rus (1)
- # lein-figwheel (1)
- # leiningen (25)
- # luminus (2)
- # lumo (5)
- # off-topic (6)
- # onyx (22)
- # pedestal (3)
- # portkey (1)
- # proton (2)
- # re-frame (7)
- # remote-jobs (1)
- # ring-swagger (3)
- # rum (2)
- # shadow-cljs (38)
- # specter (7)
- # yada (30)
I'm fairly new to Clojure/ClojureScript. So pardon me if I'm missing some obvious things... but is there a way to auto reload changed code in a Chestnut project? The cljs reloading (thanks to figwheel) is working fine. In the Chestnut readme it says that a Ring middleware is used to reload server-side code but I can't find any reference to that middleware in the code, nor do I know how the code reloading is supposed to work. Any clue? Thanks!
@robin896 the ring middleware isn't used anymore - chestnut has since moved to component. There are a few methods for reloading server side code now.
You can run (reset)
which is the reloaded workflow way. If you're under emacs+cider, (reset)
is also called when you run cider-refresh (C-c, C-x). I've also written a separate component that you can include that watches changes to your clj files and can call (reset)
for you.
@rgm looks like you'd want to interact with figwheel system api to start the autobuild programmatically - https://github.com/bhauman/lein-figwheel/blob/master/sidecar/src/figwheel_sidecar/system.clj#L299
@featheredtoast Alright, (reset) works. Thanks!