Thomas Heller

One feature that other compile-to-JS languages don't have to deal with is macros. A big part of ClojureScript is macros and a lot of CLJS libraries will have one or...

The change should only be applied at runtime so no tool should be affected. You could define the `get-expander*` fn in some namespace like `maria.eval`. Then `(set! js/cljs.analyzer.get-expander* patched-get-expander)` before...

I don't think you can get it fixed upstream. The design decision to keep them separate was made with good reason which hasn't changed. You could fix it for self-host...

Let me know if there is still any interest in this. Closing due to lack of activity.

Not sure this is still and issue, but since it was from the Closure Compiler anyways there is nothing I can do regardless.

`:npm-module` is going to stay as is. `:esm` might be a better fit in many situations, but `:npm-module` is still useful in places. Some of the quirks also have been...

Closing this as there is nothing actionable for me to do. I cannot keep up with all the different possible platforms and their own expectations. Feel free to open new...

There is no such thing as opening a browser for any regular build at the moment. Your editor might attempt it, but shadow-cljs does not as this would require an...

A quick hack would be adding that log here https://github.com/thheller/shadow-cljs/blob/51b15dd52c74f1c504010f00cb84372bc2696a4d/src/main/shadow/cljs/devtools/server/worker/impl.clj#L432 If `:runtimes` is empty it could log something else? Not sure that's where I'd want it to be ultimately but...

FWIW the "trusted" setup that parts of the closure-library use is purely for code-review purposes inside Google. They aren't actually enforced by the Compiler so you may "cheat" to get...