is there a recommended way of running other background processes (asset processors, static site builders etc) together with shadow-cljs watch?

I have used https://www.npmjs.com/package/foreman https://www.npmjs.com/package/npm-run-all in the past

nowadays I just run things separately

alright, thanks!

Hey team, is there a recommended article / resource, that goes into the “most idiomatic setup” for css with shadow? Would love any pointers!

Hey team, I am playing around with optimizing my shadow-cljs bundle. I ran

npx shadow-cljs run shadow.cljs.build-report app report.html 

{:nrepl {:port 7002}
   :builds
   {:app
    {:target :browser
     :output-dir "target/cljsbuild/public/js"
     :asset-path "/js"
     :modules {:app {:entries []}}
     :dev {:closure-defines {"re_frame.trace.trace_enabled_QMARK_" true}}
     :devtools {:preloads [day8.re-frame-10x.preload]
                :watch-dir "resources/public"}}
    :test
    {:target :node-test
     :output-to "target/test/test.js"
     :autorun true}}}

you are including cljs.analzyer and cljs.pprint somewhere

those are very heavy hitters that can't be DCE'd

so you should get rid of those at least (which will also further shrink cljs.core in the process)

Ah, thanks for the pointer @thheller! Will look deeper.

Okay, looks like the two biggers culprits: I have a /dev/…/app.cljs file, which imports

[cljs.spec.alpha :as s]
    [expound.alpha :as expound]
    [devtools.core :as devtools]))

devtools.core you should remove unless you are calling it somewhere directly?

dev stuff in general you want to move into a :preloads ns

Right now, the way it is set up, I have a custom file in /env/dev/cljs/[app-name]/app.cljs , which does the following:

(ns ^:dev/once 
  (:require
    [virtual-library.core :as core]
    [cljs.spec.alpha :as s]
    [expound.alpha :as expound]
    [devtools.core :as devtools]))

(extend-protocol IPrintWithWriter
  js/Symbol
  (-pr-writer [sym writer _]
    (-write writer (str "\"" (.toString sym) "\""))))

(set! s/*explain-out* expound/printer)

(enable-console-print!)

(devtools/install!)

(core/init!)

{:uberjar {:omit-source true
             :prep-tasks ["compile" ["shadow" "release" "app"]]

             :aot :all
             :uberjar-name "virtual-library.jar"
             :source-paths ["env/prod/clj"  "env/prod/cljs" ]
             :resource-paths ["env/prod/resources"]}

this is a terrible pattern I would strongly recommend changing

in your build config set :modules {:app {:init-fn ! :preloads [virtual-library.dev]}}

and move all the stuff you have in app to the .dev ns

no need to switch the classpath and all that mess

(enable-console-print!)

(devtools/install!)

(core/init!)

delete these 3 too. not needed at all.

…Amaazing! Thank you @thheller!

Also, with reitit-spec removed, and the dev/app stuff, now we’re muuch better: (will update with your advice and keep playing with the optimization)

Okay, current shadow setup:

{:nrepl {:port 7002}
   :builds
   {:app
    {:target :browser
     :output-dir "target/cljsbuild/public/js"
     :asset-path "/js"
     :modules {:app {:init-fn virtual-library.core/init! :preloads [virtual-library.dev]}}
     :dev {:closure-defines {"re_frame.trace.trace_enabled_QMARK_" true}}
     :devtools {:preloads [day8.re-frame-10x.preload]
                :watch-dir "resources/public"}}
    :test
    {:target :node-test
     :output-to "target/test/test.js"
     :autorun true}}}

fine to just move :preloads together. either in :modules or :devtools is fine