@braden.shepherdson but since Closure is whole program you can't partition the build really what is the benefit?

Well, the Bazel rules treat js-library as just bags of source files, and feeds them all into a final binary compilation.

I'm trying to compile my CLJS to Closure .js and include it like a hand written source file in such a build.

It works for my namespace but it's proving hard to extract the core namespaces.

(I’m not affiliated with Braden, but I’m also writing https://github.com/griffinbank/rules_clojure) Bazel doesn’t speed up the CLJS compile, but it drastically speeds up our backend Clojure build & test, and it’s very nice that the CLJS build & test steps can compose with the rest of the build

ooh a persistent worker!

that's relevant to my interests. our JVM Clojure builds are painfully slow right now and we only don't mind too much because we're using the repl for incremental development.

I'm seeing my tools.namespace fork is already being used outside of babashka ;) https://github.com/griffinbank/rules_clojure/blob/main/src/rules_clojure/parse.clj

Eventually those patches for CLJS will be merged back upstream, the first patch is sitting in JIRA already.