Skip to content Skip to sidebar Skip to footer

Webpack Breaking In Ie11

It's difficult to track this down, so thanks for bearing with me. Some users were complaining that our site was broken in IE11. The app is using nextjs 3.0.1 and webpack 2.7.0. Deb

Solution 1:

In case anyone else wrestled with this, I left the babel-polyfill in the webpack config and changed the build command to:

next build && babel .next/*.js --out-dir . --presets=es2015,react

This is pretty clunky because some code is babel-ified by webpack and then again in the output directory. Would love other suggestions!

Post a Comment for "Webpack Breaking In Ie11"