Thomas Heller

Do you have a concrete example of a library on npm doing this? I'm not against shadow-cljs supporting this. It is more an issue with the Closure Compiler itself. It...

None of those are really relevant examples meant to run in the browser where it would be relevant for shadow-cljs to process them? Are you targetting node? What build `:target`...

I'm going to need a example repro showing what you are trying to do and how shadow-cljs fails to make it work. I frankly have very little hope of shadow-cljs...

Yep, as I thought. It just fails at the next unsupported thing when I remove the `import()` check. I see zero chance that shadow-cljs will be able to bundle this.

That error exists regardless of whether shadow-cljs throws it or not. The Closure Compiler is the bottleneck here. If I remove that check and just let it proceed as normal...

Please note its the Closure Compiler. Not Clojure. You probably mean that, just making sure to avoid confusion. And yes, there are a lot of things I wish the Closure...

It is correct that shadow-cljs treats `defonce` just like `def` for release builds, as generally `defonce` only exists as a REPL aid so that reloading a namespace does not overwrite...

well, if you `def` something that only runs once as a namespace is only ever loaded once in release builds. So, `(defonce x (only-ever-runs-once 1))` works just fine.

Any estimate on this? The last maven release is over a year old and I'd like to test some of the newer stuff?

Yes, a bunch of broken stuff. Mostly from me touching parts I'm probably not supposed to touch. For example `JsAst` being rolled into `CompilerInput`, when I have a bunch of...