I believe we should drop IE11 support with the next major release. This would allow us to produce much more modern bundles.
As of June 2020 IE11 market share is only 1.4% according to https://gs.statcounter.com/
Users who really need to support IE11 would still be able to transpile our bundles or add required polyfills.
As part of this we can remove output.ecmaVersion: 5 from the webpack configs.
ctavan
All 5 comments
Users who really need to support IE11 would still be able to transpile our bundles or add required polyfills.
... or pin their dependency to [email protected]
broofa
on 19 Jun 2020
I recently saw some issues in IE11 browsers w.r.t trailing commas. Specifically with the node_modules/uuid/v4.js module. Not sure if anyone else has experienced this recently / can comment on this.
fzxt
on 7 Jul 2020
@fzxt can you provide more details? This is definitely not expected: First of all, the most recent version of this library doesn't even expose a node_modules/uuid/v4.js module, second we make sure to transpile the browser-targeted code to work well with IE11.
ctavan
on 8 Jul 2020
@ctavan just to close the loop on this, we were indeed on some old version and the errors were due to some custom setup. Sorry to necro / distract on this issue.
fzxt
on 21 Jul 2020
FYI, MSFT dropping IE11 support for MS 365 in August 2021. Source
broofa
on 20 Apr 2021
Related issues
BinitaBharati
路
9Comments
anton-marchenko
路
10Comments
ORESoftware
路
5Comments
wesleytodd
路
10Comments
guybedford
路
9Comments
Most helpful comment
... or pin their dependency to
[email protected]