Development in IE11 impossible (Blank page)

[EvertVerboven]

Is this a bug report?

Yes

Environment

1. node -v: v8.4.0
2. npm -v: 5.6.0
3. yarn --version (if you use Yarn): 0.27.5
4. npm ls create-elm-app -g (if you haven’t ejected): 1.10.1

Then, specify:

1. Operating system: MacOS Sierra 10.12.6 (Development) / Win7 Virtual Machine
2. Browser and version (if relevant): IE11 11.0.9600 In virtual machine

Steps to Reproduce

When starting the development server, and visiting 10.0.2.2:3000 in a windows virtual machine IE11 browser (maps to localhost:3000) on the actual machine a blank page shows up.

In the console the error

(Write your steps here:)

1. $ create-elm-app foo
2. $ cd foo
3. $ elm-app start
4. visit 10.0.2.2:3000 in IE11 on windows virtual machine
5. see blank page, inspect, reload to see error

Expected Behavior

I woud expect to see the create-elm-app initial page Your elm app is working

Actual Behavior

A blank page appears with an error in the console

Reproducible Demo

I did not include a demo since the issue appears immediately after creating a new elm-app.

[kspeakman]

I have this same problem. It is because the dev config does not convert some arrow functions into classic functions. IE11 cannot use ES6 arrow functions. Maybe some module is getting included after the normal build process?

Edit: Appears to do with the chalk module dependency ansi-styles, which is the source code IE chokes on.

/***/ "./node_modules/ansi-styles/index.js":
/*!*******************************************!*\
  !*** ./node_modules/ansi-styles/index.js ***!
  \*******************************************/
/*! dynamic exports provided */
/*! all exports used */
/***/ (function(module, exports, __webpack_require__) {

"use strict";
/* WEBPACK VAR INJECTION */(function(module) {
const colorConvert = __webpack_require__(/*! color-convert */ "./node_modules/color-convert/index.js");

const wrapAnsi16 = (fn, offset) => function () {
	const code = fn.apply(colorConvert, arguments);
	return `\u001B[${code + offset}m`;
};

This makes it hard to test in IE during dev. The production build does appear to load in IE.