Bradford C. Smith

Yes, I think 5 optional parameters is really the only way to declare the new single-argument version of `setTransform` in the externs.

We'd certainly entertain a PR for this one, but it's unlikely to be a priority for us.

Note that there is already an open issue for dynamic import support https://github.com/google/closure-compiler/issues/2770 I guess this one is asking for something a bit more targeted, but I'm still a bit...

@AshleyScirra do you feel this issue would be completely closed by the following behavior? If the compiler's output is set to at least `ES_2020`, then: 1. `import(anything)` will be left...

I've just successfully run ```shell cd $my_closure_compiler_git_repo git checkout master git pull --ff-only bazelisk build //:compiler_unshaded_deploy.jar` ``` I didn't see these 404 errors. I'm wondering if maybe the problem only...

Hang on a tick, I must be wrong about us configuring things to only work within Google. The GitHub actions that we have run all the time to make sure...

@blickly I believe you have some familiarity with `RandomNameGenerator`. Could you take a look at this one?

Sorry. This PR is on my to-do list, but other things keep pushing it down before I can get to it.

I've sent an internal change for review that will remove the bad "script" entries from `package.json` and the corresponding `yarn` commands from the `README.md` file. Thanks for pointing those out.

@ChadKillingsworth this change will need to be synchronized with a change to https://github.com/google/closure-compiler-npm since that repo builds and uses `compiler_unshaded_deploy.jar`. I think it should work to have it just use...