Ignore mapbox-gl transpiling

[torosyaneric]

Resolves #213

[torosyaneric]

@justinanderson I think not transpiling Mapbox is still better solution than transpiling Web Worker separately, as they say it significantly increases bundle size and negatively impacts rendering - is only considered if targeting legacy browsers.

If your application requires ES5 compatibility, then your module bundler needs to be configured to load and transpile Mapbox GL JS's Web Worker separately. This comes at the cost of significantly increasing the bundle size and negatively impacting rendering performance and you should only do this if you have a strong need for supporting legacy browsers. Mapbox GL JS can be configured with bundler specific worker-loader plugins.

[justinanderson]

@torosyaneric But do we require ES5 compatibility? How does this compare with Mapbox's first suggestion to use browserlist?

[torosyaneric]

@justinanderson it seems the browserslist approach wasn't working as our browserslist value is identical to their suggestion (+ "not op_mini all")

[justinanderson]

@torosyaneric Did you see this comment mapbox/mapbox-gl-js#10565 (comment) and the ones referencing it later from the link in the issue? It looks like Mapbox's documentation may need an update. Our production builds work with that modification, >0.2% -> >0.2% and supports es6-class.

[torosyaneric]

@justinanderson sorry, missed that one, fixed and pushed. Thanks for mentioning this.

[justinanderson]

@torosyaneric But, I mean, what's the difference between the two options? I don't have much experience with transpilation concerns and would like to understand the choice we're making.

[torosyaneric]

@justinanderson I'm not 100% percent sure but I suppose using browserslist approach prevents the transpilation for whole codebase by rule "supports es6-class" and "import from !mapbox" was just ignoring the mapbox transpilation. I don't think these have advantages in terms of bundle size, maybe in build time.
Do you want me to investigate this further?

[justinanderson]

@torosyaneric Nah, this is fine. I spent some time to learn about transpilation and feel I understand it well enough now.

It looks like we can safely ignore browsers which don't support ES6, so I'll take this as is.

[justinanderson]

Force-pushed to remove noop commit and allow this branch to rebase cleanly.