New Calva just out, dear Calva friends: https://github.com/BetterThanTomorrow/calva/releases/tag/v2.0.288 • https://github.com/BetterThanTomorrow/calva/issues/1785 • https://github.com/BetterThanTomorrow/calva/issues/1791

I'm trying to figure out a common webworker usage patter across all the different build tools (cljs.main, figwheel and shadow) and for cljs.main, I can't figure out how to get calva's deps.edn + Clojurescript built-in for Browser option to pick up a build.edn file, per this example here: https://github.com/kommen/clojurescript-webworker-demo The recommendation there is to do:

clj build.clj
clj -M -m cljs.main --serve localhost:7777

Correction, that example project advises to run the build.clj which has compiler options passed to the build fn. But I'm wondering if it's possible to pass the options in somehow to the repl-env in the repl connect sequence

Hmm, yeah, seems like there's some regression in cljs.main where you have to use cljs.build.api/build atm, so clj -M -m cljs.main -v -co build.edn -c -s doesn't work currently in that example project. I am however able to spawn a webworker programmatically though, after the artifact is built and loaded on the main thread, using a static loader file to pull in the deps.

Is there any reason why the calva terminal in a WSL Remote won't log anything after my server starts up? Either it's an extension issue with WSL Remote or a logger problem

I don't use dev containers btw. Just my WSL Ubuntu default