Ashley (Scirra)

This also affects us - since the JavaScript version of Closure Compiler (jscomp.js) was retired, we're looking in to getting our own JavaScript/WebAssembly port of Closure Compiler. The jar file...

Is that an undocumented option? [The flags and options documentation](https://github.com/google/closure-compiler/wiki/Flags-and-Options) doesn't appear to reference it.

What's the difference between NO_TRANSPILE and setting both the input and output language to the same thing?

Here is what I've found with past releases: v20210202 > Added experimental support for allowing dynamic import expressions import('./path') to pass through the compiler unchanged. Enabling this requires supplying the...

The same goes for `import.meta` too - we also need to use `import.meta.url`, but the fact all compilation fails if it's present anywhere is a major limitation. That should be...

Just want to link to [this comment](https://github.com/google/closure-compiler/issues/3708#issuecomment-713488361) here as well - for the "just minify" case I think it would be fine to have a flag that just says "pass...

I think #2770 is asking for full support. I'm only asking here for Closure Compiler not to fail compilation due to the presence of dynamic import, i.e. the minimum possible...

Yes, that sounds like it would do it.

Rolling back a few versions and found: [email protected]: OK [email protected]: broken So looks like a regression in 0.4.1.

Based on version range suspect this commit: https://github.com/babel/minify/commit/552766955c011618f86c0f39451b9e288383c67a