Sébastien Doeraene

Ping @dwijnand ?

Thanks 🙏

No news, I'm afraid. This is currently not a priority, as it is a non-functional requirement. We are focusing on functional requirements until 1.0.0 is released.

It might be acceptable in a number of situations, yes. But since it won't produce the same code after a `clean`, I think it should behind some sort of flag,...

Yes, this is a known limitation of the version of Closure that we use. A PR that upgrades GCC and manages to make this work would be welcome.

Yes, it does.

There is support for ES 6 (official name ES 2015) except modules. We do enable GCC for ES 2015 code, which is even the default in Scala.js 1.x. We disable...

I think the discussion at https://github.com/google/closure-compiler/issues/2770 means that it's simply not supported by Closure.

I'm afraid I don't any direct contact in the Closure team. However, I've a good experience reporting issues and sending PRs to fix things. In this case it's a feature...

That workaround could work for dynamic imports, but what about static `import`s of ES modules? I guess we would have to not include them in the code being compiled by...