title: Angular 2+: IE 11 Unable to get property 'call' of undefined or null reference
body: <p>I'm having an issue with Internet Explorer choking on something with Webpack. I'm using Angular-CLI 1.7.4, and Angular 5.2.10, the current versions. I'm getting this error:</p>
  
  <blockquote>
    <p>SCRIPT:5007 Unable to get property 'call' of undefined or null
    reference. Inline bundle.js (55,12)</p>
  </blockquote>
  
  <p>This is different than <a href="https://stackoverflow.com/questions/44531082/angular-2-internet-explorer-unable-to-get-property-call-of-undefined-or-nul">this issue</a>, in that it is on a different line in the bundle. The line looks like this:</p>
  
  <pre><code>/******/        modules[moduleId].call(module.exports, module, module.exports, __webpack_require__);
  </code></pre>
  
  <p>I tried modding the webpack code in the <code>node_modules</code> to <code>console.log</code> the <code>moduleId</code>, but it doesn't log for some reason.</p>
  
  <p>I found <a href="https://github.com/webpack/webpack/issues/959" rel="nofollow noreferrer">this thread</a>, where a lot of people are dealing with this issue. I'm not able to see what is relevant to my issue.</p>
  
  <p>I do not have any circular dependency warnings from the CLI.</p>
  
  <p>I've reverted my code to several different previous versions, reinstalled the node modules, and I still get the same error. That's really strange.</p>
  
  <p>UPDATE: Here are the polyfills I have in:</p>
  
  <pre><code>import 'core-js/es6/symbol';
  import 'core-js/es6/object';
  import 'core-js/es6/function';
  import 'core-js/es6/parse-int';
  import 'core-js/es6/parse-float';
  import 'core-js/es6/number';
  import 'core-js/es6/math';
  import 'core-js/es6/string';
  import 'core-js/es6/date';
  import 'core-js/es6/array';
  import 'core-js/es6/regexp';
  import 'core-js/es6/map';
  import 'core-js/es6/set';
  import 'core-js/es6/reflect';
  import 'core-js/es7/reflect';
  </code></pre>
  
  <p>I also found <a href="https://github.com/angular/angular-cli/issues/7776" rel="nofollow noreferrer">this issue</a>, which shows that a number of people are having this problem, and the solutions offered are not working.</p>
  
  <p>UPDATE: I've found the reason the console.log wasn't being called from Webpack. It's that it wasn't necessarily <em>in</em> Webpack. I searched my <code>node_modules</code> for <code>modules[moduleId].call(module.exports, module, module.exports, __webpack_require__)</code>, and found there were 87 occurrences. I assumed that because it said 'webpack' that it was part of webpack, so that was the first place I looked, which is a place where it <em>does</em> occur, so I stopped there thinking I'd found it.</p>
  
  <p>Also, I'm having this problem again, and restarted my Angular-CLI server a bunch of times, but I'm not able to get a compile that is working.</p>
  
  <p>This is becoming critical, so I'm going to raise a bounty on this question.</p>
  
  <p>UPDATE: It looks like IE is choking on the invocation (<code>Function.prototype.call</code>) of the method that adds the polyfills. I captured this from inline.bundle.js. It's one of the first things that happens:</p>
  
  <pre><code>function(module, exports, __webpack_require__) {
  
      module.exports = __webpack_require__("./src/polyfills.ts");
  
  }
  </code></pre>