Thomas Heller

`shadow.test/run-test-vars` is on the only relevant function here. `run-tests` does something different and will not be adjusted to do something else. However I'm totally open to adding additional helper functions...

Yes, you are missing my argument here. I'm not going to modify `shadow.test/run-all-tests` because all default test runners use it. I'm willing to add a different mode that uses a...

Please explain what you actually intend to happen without using `kaocha`. I don't know how it operates or what effects those config settings have. Like what is `:focus` actually doing?...

And what is the rest of the workflow? Is it running in watch mode compiling all namespaces but only running marked tests or do you trigger the test execution manually?...

I'm not against adding support for `.wasm` but its probably not going to be part of `ns` `:require`. The `.wasm` files I have seen to date are either tiny toy...

Did some experiments yesterday since this [example](https://github.com/gklijs/game-of-life) was posted in the #shadow-cljs channel. It is a `.wasm` file generated by Rust tools and as expected the problem is not so...

Most recent update looking at `.wasm`. Getting better but still not smooth. Likely still ways off till I can actually support this in `shadow-cljs` directly. https://github.com/thheller/wasm-pack-cljs

It is still solely dependent on what the "glue" JS looks like. Until this is standardized each X-to-WASM compiler will do its own thing and that hasn't changed much AFAICT.

That code already exists. There is no test for this so it might not work anymore. I haven't checked yet. https://github.com/thheller/shadow-cljs/blob/72176ad9b33c2214cf91bd24b0f90f65aaa3a114/src/main/shadow/build/resolve.clj#L421-L432

Hmm, that is an error from the Closure Compiler. I don't have an immediate idea which part it doesn't like. Also nothing I can do from the shadow-cljs side of...