Thomas Heller

Regular JS tree-shaking is very limited. It is not comparable to the Closure Compiler `:advanced` optimizations, and recognizes very few patterns. That works when you write code specifically for it,...

> Another point of consideration is that all of the current minimization tools (including the two above) are basically on par or sometimes slightly better at minimizing JS code than...

> ... , but it's running benchmarks against nontrivial JS code That is missing the point. The point of this thread and my comment is tree-shaking or dead code elimination,...

The jar is definitely available. Seems like maybe a download got interrupted somehow and you have an incomple file? You can delete the `~/.m2/repository/thheller/shadow-cljs/2.19.9` directory so it fetches everything again?...

I created an example v3 extension. See https://github.com/thheller/shadow-cljs/issues/1051 I made no attempt at `eval` but `:target :chrome-extension` should be considered obsolete by now and `:target :esm` seems to be the...

Closing this because I think `:chrome-extension` is no longer needed. V3 extensions can use ESM just fine and that should be the way forwarnd. See https://github.com/thheller/shadow-cljs/issues/1051.

The IE11 issue was solved. Just kept this open due to the discusses build time difference. Closing since there really isn't anything actionable to do here. Can't reproduce any slowdowns...

I'm guessing the behavior that confuses cider is that when an error occurs it sends the error message via `:err` messages and then `:repl/exception!` as the final "result" value. I'm...

Hello everyone. The request to be able to publish/consume CLJS packages via npm instead of clojars has come up quite a lot for `shadow-cljs` as well. I'm sort of opposed...

> Tell people where the bulk of your library is. Nothing special is done with the lib folder in any way, but it's useful meta info. As I said the...