This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (25)
- # boot (14)
- # business (1)
- # cljsrn (2)
- # clojure (180)
- # clojure-korea (14)
- # clojure-russia (8)
- # clojure-spec (9)
- # clojure-uk (17)
- # clojurescript (110)
- # cursive (14)
- # datomic (18)
- # emacs (23)
- # events (4)
- # garden (7)
- # hoplon (44)
- # lein-figwheel (1)
- # liberator (4)
- # london-clojurians (1)
- # om (10)
- # om-next (2)
- # onyx (22)
- # protorepl (60)
- # re-frame (36)
- # reagent (11)
- # ring (10)
- # yada (5)
@aengelberg Checkout task works the same, files are added to classpath so c.t.n/refresh will work
The benefit in Boot implementation is that checkout task can use both packages from Lein and Boot, file Lein checkouts only works with other Lein projects
In Lein, changes to cljs files in checkouts don't trigger automatic recompilation if I recall correctly
@aengelberg if your other (checkout) lib also uses boot you can use something like
boot watch pom jar install to continiusly install into
Good news, I had a couple of very good sessions working on boot-reload's support for figwheel client and thanks to the Conj I can now reload js files. TODO: css and maybe deps.js (figwheel sends it at some point)
wait, so I do need some additional process to be continuously installing into
~/.m2 in order for reloaded.repl to work across subprojects?
When I get the change, I'll just try some stuff out and see for myself what the limitations are exactly.
@aengelberg yes you need the other process if you want to use checkouts. Another alternative is to just add the path to the project to
:source-paths or similar but then you would need to make sure all dependencies are satisfied yourself.
@richiardiandrea sounds awesome! I assume the main benefit over current boot-reload behavior would be better error messages?
@pesterhazy yes and if we extract the client and make it a common thing it is easier to add features/fix bugs, more interest from both user bases