Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

drop support for Internet Explorer and Edge Legacy

See original GitHub issue

The rest of the platform is dropping IE support.

We currently transpile to ES5 for the sake of IE and ship that as ESM, CJS, and UMD modules. What should we start transpiling to? ES2015? ES2016 (Array.includes)? ES2017 (async/await)?

Would be good if anyone’s aware of how other isomorphic libraries have handled this.

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

gavinrcommented, May 13, 2021

Node.js version 10 end-of-life date was April 30, 2021, so safe to support 12+ at least. Note that this page mentions Node v8+ (incorrectly), so we should update that doc as part of this.

I think this means we would drop the UMD build entirely

Many of our samples use the UMD version in a script tag, for example https://esri.github.io/arcgis-rest-js/guides/from-a-cdn/ - what would be the recommended replacement code for these?

1reaction

patrickarltcommented, Dec 17, 2020

ES2015 (97.6% of browsers) vs ES2017 (94.8% of browsers) are REALLY similar. I kinda feel like we should just make a clean break and do ES2017. If people want to use the 2.x version they 100% can if they really feel they need that browser support.

We should also bump Node to 14.x or 16.x. Either support ES2017 but as far as I know the highest node version any Esri internal team is using is Node 14.