This might be useful for someone. I had problems with boot-cljs slowing down my build when I was trying to iterate writing styles using garden & having the styles reload in the browser.

(defn switch [switch-atom switched-task]
  (let [init (atom true)]
    (fn [next-handler]
      (fn [fileset]
        (if (or @init @switch-atom)
          (do (reset! init false)
              ((switched-task next-handler) fileset))
          (next-handler fileset))))))

(def cljs-every-build (atom false))

(deftask build-frontend
  []
  (comp
   (build-styles)
   (switch cljs-every-build (cljs))))

You can reset the atom from the repl, turing that task on or off.

@seancorfield - IIRC you mentioned once working on a monorepo system with sub-projects having their own deps, etc. and gluing it all together with boot. Have you got a gist or writeup somewhere to share some of those details? Or anyone else for that matter 🙂 I’m specifically interested in working with a monorepo where each project could theoretically have its own deps (clj / cljs / npm) and generate its own artifacts. Not sure if its a good idea, thoughts?

@pithyless yes we are working on that but it's slow progress because it all works already with boot and other things are higher priority. We have a branch where the first few subprojects in the monorepo have been converted.