Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: webpack: IE11 fixes and workarounds #3481

Closed
wants to merge 3 commits into from

Conversation

rmader
Copy link
Contributor

@rmader rmader commented Mar 11, 2021

From the first commit:

Webpack 5 dropped ES5 polyfills, required for IE11 support. Explicitely
specify ES5 support (`target`), making Webpack complain about everything
that's missing. Install all required polyfills and make Webpack fall
back to them.

Sad thing is that we loose chunk dependencies again, resulting in bigger js files (like we had before #3440) and, because we now transpile almost all js (but mapbox because of a bug in babel), in longer build times, even during development.

The last point, longer dev build times, can probably be circumvented by moving the babel-loader config to production settings only.

Closes #3441

Webpack 5 dropped ES5 polyfills, required for IE11 support. Explicitely
specify ES5 support (`target`), making Webpack complain about everything
that's missing. Install all required polyfills and make Webpack fall
back to them.
@rmader rmader mentioned this pull request Mar 11, 2021
@rmader rmader changed the title webpack: IE11 fixes and workarounds WIP: webpack: IE11 fixes and workarounds Mar 11, 2021
@philli-m
Copy link
Contributor

@rmader is this still WIP? Also once we do not need to support IE11 anymore, would you say we could just rebase and implement #3462 ? obviously after extensive testing

@rmader
Copy link
Contributor Author

rmader commented Mar 11, 2021

Yeah I'm sorry, looks like this is blocked by parcel-bundler/parcel#1128 (there are a few similar bugs in different projects). Short story is that if we transpile all js dependencies (so it's compatible with IE11) we run into some babel error. It might be possible to somehow exclude all relevant packages, but I still haven't managed to pick the right ones. Another option is to wait and hope this gets fixed in babel.

Either way I don't quite find a solution that makes IE11 work properly in embeds (and other areas) while not breaking mapbox for all browsers :(

@philli-m
Copy link
Contributor

We no longer have to support IE11 so will close 🎉

@philli-m philli-m closed this Mar 25, 2021
@fuzzylogic2000 fuzzylogic2000 deleted the rm-2021-03-ie11-embed-error-2 branch July 8, 2021 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bplan statement form blank on IE 11
2 participants