Thomas Heller

This seems to be including some code meant for `node`? `@aws-sdk/hash-node` probably isn't meant to be used in a browser environment? I don't know any of these packages. Are you...

I don't even know where to begin debugging this mess of a package that is `aws-amplify`. You are probably better off using webpack as described [here](https://code.thheller.com/blog/shadow-cljs/2020/05/08/how-about-webpack-now.html#option-2-js-provider-external).

You can use `:maven {:mirrors ...}` in `shadow-cljs.edn` or `~/.shadow-cljs/config.edn`. The `:maven` map takes the same options as leiningen would in its place. So `:proxy` is supported as well. Don't...

What is the particular issue blocking you from accessing maven directly? And what is the particular problem with maven configuration? Do you have access to a mirror or a proxy?...

This really only affects the npm cli version so it is possible just use the older npm package with newer shadow-cljs jars. Since you are using deps.edn anyways you can...

Well, you'd have to look at the Closure Compiler changelog for that one since they removed it. Don't remember when.

FWIW I wrote a script to generate a changelog from git commits. https://github.com/thheller/shadow-cljs/blob/master/CHANGELOG.md Still need something to automate git tag/release generation. Haven't looked into that at all yet, definitely not...

Yes, invoking stuff in the REPL may affect the build in unexpected ways. This one is particularly nasty since it sticks arround until you actually modify the file that had...

Perhaps the place to check for this is the [default test runner](https://github.com/thheller/shadow-cljs/blob/086ee94f9a4e5fac66a9c4fa985364a40ab41ce4/src/main/shadow/test/node.cljs) from `:node-test`. It already does some test filtering based on some command line arguments. `env/get-test-data` is supposed to...

Also note that the limiting factor here seems to be `karma`? Otherwise you can just run a single test in any REPL directly without any test build or runner whatsoever....