Thomas Heller

Note that you can just add the "fixed" dependency to your own dependencies. This will just override whatever shadow-cljs might bring in by default. There is no need to do...

I dug arround a bit and found that nrepl just executes all received messages in a thread pool. It may therefore already read the next message before the `shadow-remote-init` has...

I just made the `3.2.1` release which should be sending `:done` status messages and seems to include things in `describe`. Let me know if something else makes sense.

`shadow-remote-init` is not related to builds in any shape. `shadow.remote` itself isn't either. There is the concept of a `relay`, which everything connects to and will then route all the...

> I think I may have tried to initialize the remote a bit too early, because I had some more flakyness with this. I think I should clarify how all...

If you are not using the `:request-clients` reply you might as well switch the initial msg to `{:op :request-notify :query ...}`. That'll just setup the notifications. The `:notify true` bit...

How do you actually handle the startup sequence? I mean technically the middleware could just `start!` itself if needed. Just wondering how you handle all this in a deps.edn custom...

Thanks for the breakdown, much clearer picture now. Minor tweak, but may make things a little nicer. ``` (doseq [build [%BUILDS%]] (shadow.cljs.devtools.api/watch build {:sync false}))) ``` The `{:sync false}` bit...

The `watch` worker maintains the runtimes it knows about here. https://github.com/thheller/shadow-cljs/blob/425740ca9a0096aeeae5d5134f3531cfce5baa6b/src/main/shadow/cljs/devtools/server/worker/impl.clj#L771-L799 Basically all the logic you asked about is here. "no JS runtime" is the error you get when an...

> I am probably misunderstanding, but it sounds on your description that when there are several runtimes available and connected to shadow-cljs, a new one would automatically get connected when...