how can I tell shadow-cljs don't log debug level?

https://github.com/thheller/shadow-cljs/blob/a5b266efd8c042d3438ec2ba7c32cb4c17d73edb/src/main/shadow/cljs/devtools/server/nrepl.clj#L344 I don't want this log, it will be showed in the REPL, a little annoying.

@doglooksgood debug log should not be enabled by default? when using embedded lein however you are in charge of configuring your logging

@wilkerlucio yeah I was going to add that

is there a recommended strategy to have multiple watched builds at the same time? for example i have a test build (`:karma`) and a :browser build and I'd like them both to run continuously in the background

at the moment i just have two separate processes and maybe that's the way to go, i was just wondering whether there's a better way

shadow-cljs watch karma browser

oh. maybe i should have just tried that haha

Has anyone here built a shadow app as a docker image with drone?

How does shadow pick up transitive npm deps? Or perhaps rather, does it?

If I depend on libraryA which depends on npm dependency X, how should that be communicated?

@dominicm shouldn't dependency x be installed when you install npm install -S libraryA? I mean the whole npm ecosystem is managed by npm and shadow-cljs provides a bridge to it

is there a way to update dependencies in a running watch? via the clojure api?

@arne-clojurians I have a clojurescript libraryA, which depends on npm X

I figured it out, deps.cljs supports :npm-deps key.

do node packages with dashes in their name require special treatment when :requireing? nvm

hmm, when I put :asset-path to "/", it tries to load scripts from

(i’m trying to compile a service worker which needs to be at the root of the site)

& empty string throws a config error