I have a boot cljs project building both :optimizations :none and :optimiozations :advanced. I want (dirac.runtime/install!) + (devtools.core/install!) + dependencies to ONLY be in the :opt-none build, and NOT in the :opt-advanced build. How can I configure this?

I have a cljs project with with node js as the target. for development, how can I run node with boot.util/sh after the project is built, but only once, so that node isn’t started every time a file changes and watch triggers?

so when do you want to shell out to node?

can you post your pipeline?

@pesterhazy this is my pipeline

(def backend-target "/build/backend")

(deftask backend-dev []
  (merge-env! :source-paths ["clj/backend/src"])
  (comp
   (with-post-wrap fileset
     (binding [*sh-dir* backend-target]
       (sh "node" "backend"))
     fileset)
   (watch)
   (reload :ids ["backend"] :on-jsload 'backend.core/main :port 7890 :disable-hud true)
   (cljs :ids ["backend"])
   (target :dir #{backend-target})))

what happens, and what would you prefer to happen?

with this, (sh "node" “backend”)) is never executed. And I would expect it to be executed once after target has written the fileset the first time to backend-target

ah

yeah that won't work because watch starts a loop of the following tasks, and it's an infinite loop

what you can do is

to create a task with a delay which derefs that delay, and add that task at the end of the pipeline

that way, the body of the delay will only be executed once, i.e. after your target dir was written

(deftask run-node [] (let [d (delay (sh "node" ..))] (with-pass-thru [_] @delay)))

@pesterhazy thanks! that worked

do you have boot-reload working with node?

well, it worked at some point, but it looks like it’s broken right now for me here

interesting, does it work with websockets, just like in the browser?

yes

cool I should check it out sometime

It would be great if boot-figreload works with node as well

@pesterhazy I can’t figure out if/how reload would have ever worked for me with nodejs. maybe I’m just confusing with having it working with figwheel. (I just moved the whole project from lein to boot)

I mean with node and lumo I can now just attach using the socket repl, which works ok