Drop IE11 support
See original GitHub issueI 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.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:8 (6 by maintainers)
Top Results From Across the Web
IE11 end of support countdown
Sources before May 19th 2021 · Support for older versions of Internet Explorer ended · Windows 10 product lifecycle · IE11 Mainstream End...
Read more >Should you drop support for Internet Explorer 11?
Should your app or service continue to invest time in Internet Explorer 11 support? The answer is: it depends. Find out more here....
Read more >Dropping support for Internet Explorer 11
When WordPress 5.8 is released in July of this year, Internet Explorer 11 will no longer be supported. If you are currently using...
Read more >AWS is dropping support for IE11, so get ready to switch ...
AWS is phasing out IE 11 support from July 31 through to July 31, 2022. This week, it stopped testing whether IE 11...
Read more >Dropping support for Internet Explorer 11 (when 18% of your ...
At Culture Amp we dropped support for Internet Explorer 11 in March this year, despite a significant portion of our annual recurring revenue ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
… or pin their dependency to
uuid@v3.4.0
@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.