@jmckitrick Or macchiato? 🙂

I have a project that has stopped building when run in a container, with no obvious cause:

Step 7/14 : RUN npm install --save-dev shadow-cljs && shadow-cljs release client server
 ---> Running in 2718b0f65743
npm WARN app No repository field.
npm WARN app No license field.

+ [email protected]
removed 4 packages and updated 1 package in 5.35s
shadow-cljs - config: /app/shadow-cljs.edn version: 2.3.21
shadow-cljs - starting via "clojure"
Removing intermediate container 2718b0f65743
 ---> e1034d53eece

@theasp it might discard the error message when clojure is missing? maybe thats not available

Yeah, thats exactly it

I was about say that 😉

please open an issue for this so I don't forget to fix it

Sure!

This "installing clojure" thing seems bizarre now

Damn, the official clojure docker image doesn't have it either

What happens if the clojure version doesn't match the version in deps.edn?

1.9 is required due to spec

but the script version itself is all 1.9 anyways I think

but the script clojure version doesn't affect your version at all.

any way to disable CLJS DevTools?

@thheller Is there a way to get shadow-cljs to download deps, without building?

Maybe this is all I need: clojure - <<<"nil"

Yeah, that does it!

@kanwei :devtools {:enabled false}

or do you mean these? https://github.com/binaryage/cljs-devtools

yeah binaryage ones

i already turned off :devtools

:devtools {:console-support false} or not putting them on the classpath should do it