if you have a function in the user(.clj) ns like

(defn watch-foo
  {:shadow/requires-server true}
  []
  (shadow.cljs.devtools.api/watch :foo))

you can also send processes to the background using good ol' terminal commands https://linuxhandbook.com/run-process-background/

the shadow-cljs start command is nice because you can stop a watch without stopping the server, meaning starting other watches is fast

Exactly, this is why I'd like to start the server independent from starting/stopping watches. Since I want to integrate that with other tooling, running watch in the background is not feasible I fear. @UAEH11THP - this looks interesting, will have a look

@U922FGW59 I'm not sure what you mean "running watch in the background is not feasible I fear."

I meant:

shadow-cljs watch my-build &

right, why can't that work?

if you start the server first, your watch will connect to the server and when you stop the watch it will not stop the server

For example, if you want to run this from a babashka script

I don't understand what you mean by "running in the background at the CLI" then

When I start a server with shadow-cljs start, it starts in the background. I can then go to the UI and start a watch, without having to keep a terminal open for the watcher. I'd like to have the same behaviour at the CLI: To start/stop a watcher without binding the watch to my terminal

idk i'm clearly missing something.

if you're running shadow-cljs watch my-build directly from your terminal, then adding & at the end will start it in the background. if you're using babashka to run it, then you should be able to start the babashka process in the background. but i don't really understand what you mean at this point, so i'll let others try and help

even if you & a process if you close the terminal doesn't it get killed? when you shadow-cljs run a function that :shadow/requires-server, the server will process it and your cli command (the shadow-cljs run) will exit almost immediately

Hm, weirdly this custom script solution does not work for me either. It compiles, but does not start a watcher?! n/m looked at the wrong place

https://shadow-cljs.github.io/docs/UsersGuide.html#warnigs-as-errors ?

The docs show how to ignore certain ns, and what warnings to ignore

But there’s no way to specify “in this ns, only ignore this warning. In this other ns, only ignore this other warning”

Unless i am misunderstanding the docs

right, no thats not supported.

warnings are also supposed to be fixed, not ignored 😛

Marking a fn as deprecated is a different level of warning than using an unbound var

Or a lib shadowing a new var in clojure.core