Brandon Ringe

@Vatyx Hmm. With just clojure-lsp running and no repl connection, I can reproduce your issue (and maybe that's expected with clojure-lsp's navigation functionality - I'm not sure). With a repl...

> - Calva prints Waiting for Shadow CLJS runtimes, start your CLJS app... in a loop > - When I scroll up to read the ClojureScript error message, Calva will...

@denizoz There was a [related change](https://github.com/BetterThanTomorrow/calva/pull/2060) in 2.0.330. Can you tell us if the problem persists for you in this version? Can you also test this, @chadkennedyonline? I don't know...

> Shall we try to release this behind an opt-in setting as quickly as we can? Sorry, I'm moving slowly with this so far due to being busy with other...

@PEZ Do you have time to look at this soon?

I've found that it fails every time for a work project, which I can't share. I also found that it fails every time from the extension development host when running...

> Is it some particular project open in the extension development host when this happens? I think it was the aforementioned work project open in the development host 🤦.

> The commented line is quite hard to parse as a human as the lack of syntax highlighting means I need to read the whole line to find the info...

Interesting things I see: * `TypeError: e.filter is not a function` - I see this in several places, coming from Calva. * `ERR Cannot read property 'start' of undefined: TypeError:...

You should be able to just clone Calva, open the repo in VS Code, then run `ctrl+shift+b` (Run Build Task), and once that says it's watching for file changes, hit...