I've been attempting to launch my Angular 8 application on Internet Explorer 11. Despite following all the outlined steps in this informative article, Angular 8 and IE 11,
I am still encountering errors as shown in this screenshot ->IE console
Below are the pertinent files :
Polyfills.ts:
/***************************************************************************************************
* BROWSER POLYFILLS
*/
/** To support NgClass on SVG elements in IE10 and IE11 */
import 'classlist.js'; // Execute `npm install --save classlist.js`.
/*
* Web Animations required for `@angular/platform-browser/animations`
* Essential only if AnimationBuilder is utilized within the app and dealing with IE/Edge or Safari.
*/
import 'web-animations-js'; // Run `npm install --save web-animations-js`.
** The subsequent polyfills are needed for IE9, IE10, and IE11. **/
import 'core-js/es/symbol';
import 'core-js/es/promise';
import 'core-js/es/object';
import 'core-js/es/function';
import 'core-js/es/parse-int';
import 'core-js/es/parse-float';
import 'core-js/es/number';
import 'core-js/es/math';
import 'core-js/es/string';
import 'core-js/es/date';
import 'core-js/es/array';
import 'core-js/es/regexp';
import 'core-js/es/map';
import 'core-js/es/weak-map';
import 'core-js/es/set';
import 'zone.js/dist/zone'; // Integrated with Angular CLI.
BROWERSLIST:
// > 0.5%
last 2 versions
Firefox ESR
not dead
IE 9-11 # For supporting IE 9-11, remove 'not'.
TSCONFIG.JSON:
{
"compileOnSave": false,
"compilerOptions": {
"baseUrl": "./",
"outDir": "./dist/out-tsc",
"sourceMap": true,
"declaration": false,
"downlevelIteration": true,
"experimentalDecorators": true,
"module": "esnext",
"moduleResolution": "node",
"importHelpers": true,
"target": "es5",
"typeRoots": [
"node_modules/@types"
],
"lib": [
"es2018",
"dom"
]
},
"angularCompilerOptions": {
"fullTemplateTypeCheck": true,
"strictInjectionParameters": true
}
}
WEB.CONFIG:
<?xml version="1.0" encoding="utf-8"?>
<!--
...
ANGULAR.JSON:
{
"$schema": "./node_modules/@angular/cli/lib/config/schema.json",
...
PACKAGE.JSON
{
...
**The provided solution should be compatible with ng build.