1. I was using the `deps + shadow-cljs" connect sequence, is that insufficient?

2. TIL that I can launch my server and connect browser successfully even after the timeout warning:

; Please start your ClojureScript app so that Calva can connect to its REPL...
; Waiting for Shadow CLJS runtimes, start your CLJS app...
; Waiting for Shadow CLJS runtimes, start your CLJS app...
...
; Waiting for Shadow CLJS runtimes, start your CLJS app...
; Timed out waiting for Shadow CLJS runtimes, pretending we are connected.

What even is the timeout, is it a timeout on Calva trying to reach the browser? Why does that matter? The connection will come when it comes, just leave the repl in CLJ mode until I ask for CLJS

3. What does the shadow-cljs boot sequence actually do (as compared to deps + shadow-cljs? How is shadow invoked?

1. The only practical difference is that it shadow will print the repl process output in the terminal rather than them being sent back as repl messages and printed in the REPL window. It might matter in your case because the warning messages that the scroll reset is preventing you from reading would be printed in the terminal instead. 2. The Waiting messages solves a Ux problem we had with users missing that step to complete the connection. I’m a bit reluctant to change this right now, because of a lack of ideas how to address the problem instead. We’re probably going to change the REPL/Output window implementation quite a lot soon, and will have more UI/Ux tools at our disposal then. 3. As long as shadow-cljs is set to use deps for its dependencies, the two sequences are pretty similar. With deps + shadow-cljs, Calva will start the clojure process, and shadow-cljs will be started from the repl via the shadow-cljs api. With shadow-cljs Calva will start a shadow-cljs process and shadow-cljs will start clojure. Afaiu the only practical difference is the one mentioned in 1. I’m elaborating a bit on how these things are wired here: https://blog.agical.se/en/posts/shadow-cljs-clojure-cljurescript-calva-nrepl-basics/ Me, I prefer to have shadow-cljs printing its output in the terminal, so I always use the shadow-cljs sequence.

so that means with standalone shadow-cljs process you'll get two jvms right? That won't work with Electric

I don’t think VS Code allows it. What I do is that I evaluate the file (the command Calva: Load/Evaluate Current File, ctrl+alt+c ctrl+alt+c) and then use the command Calva: Send Current Top Level Form to Output/REPL Window, ctrl+alt+c ctrl+alt+space, to get the function over to the REPL window and edit and evaluate it there.

Is the dependency in your main deps or only your test deps? If the latter, did you tell Calva to include test deps when you jacked-in?

Hi Sean, so the dependency is in the main deps, and I'm not sure how to include it in the test deps :thinking_face:

Hmm, if it is specified in the main deps then it should be available in the REPL with no special ceremony. Is this a project.clj or deps.edn project? Can you share that file? Or link to this project if it's on GitHub?

You have this dependency?

(~/clojure)-(!2010)-> clj -Sdeps '{:deps {org.apache.kafka/kafka-streams-test-utils {:mvn/version "RELEASE"}}}'
Clojure 1.12.0-alpha4
user=> (import '(org.apache.kafka.streams TopologyTestDriver))
org.apache.kafka.streams.TopologyTestDriver
user=>

(perhaps with a specific version?)

So, we are using repl profile from project.clj in order to use repl and calva, and I've added the kafka-streams-test-utils to :dependencies of this profile and it worked! Thanks so much for the tip! :star-struck:

Thanks for sharing! There are no settings in Calva for this, but there’s at least one issue around adding options for output. See if you find it and add any input you have, please.