Removing unused catch params breaks JS on older Apple devices

[kamermans]

Hi, thanks for all your hard work!

I noticed you recently removed try/catch params if there are no parameter bindings: 2e77ff3

This produces statements like this:

try {
   1/0
} catch {
   console.log('Oops!')
}

This code is valid in most browsers, but not in older Apple devices (Safari on desktop or iPhones / iPads). So far this is the only incompatibility I've noticed when minifying JS for these platforms, and my only workaround is to explicitly reference the parameter so the minifier doesn't drop the param.

Here's what it looks like in a Safari console:

I'm not sure what level of compatibility you're aiming for, but if we could put this behind a flag or handle it differently, that would be great!

I am a Go developer, so if you'd like a PR, just let me know what path you'd like to go down.

[kamermans]

This problem might be more widespread than I first thought. According to the sites I've checked, Optional Catch Binding was introduced in ES10 in 2019.

https://caniuse.com/mdn-javascript_statements_try_catch_optional_catch_binding

[tdewolff]

Thanks for the issue, this should now be fixed by passing the Version = 2018 option to the JS minifier.

[kamermans]

Awesome, thanks @tdewolff!