Any Angular 4/5 gurus on here

Stephen

Expert Member
Joined
Nov 7, 2006
Messages
2,470
Reaction score
1,535
Hi All

This is getting me to pull my hair out.

Using the Angular CLI i installed the boiler plate app using - ng new projectname

I am using no Angular Animation nor am i working with SVG's. Its a plain jane Hello World type app

I have uncommented those lines for Internet Explorer in the polyfill.js file. It works fine in IE 11, but not in 10 or 9

angular-ie10-error.jpg

angular-ie10-error2.jpg

Here is my tsconfig.json file:

Code:
      "compilerOptions": {
        "outDir": "./dist/out-tsc",
        "sourceMap": true,
        "declaration": false,
        "moduleResolution": "node",
        "emitDecoratorMetadata": true,
        "experimentalDecorators": true,
        "target": "es5",
        "typeRoots": [
          "node_modules/@types"
        ],
        "lib": [
          "es2017",
          "dom"
        ]
      }
    }

Angular suppose to cater for I.E 9 and 10

Thanks
 
You have 5 options.

Option 1. 2Pac - Changes
Remove webpack from your build script. But keep babel.

Option 2. Mark Morrison - Return of the Mac.
Check your polyfills and config for webpack/babel, and add any that may be missing... Enable legacy flags etc etc.

Option 3. Snoop Dogg - Drop it like it's hot.
Remove IE9/10 support.

Option 4. Shaggy - Wasn't me.
Ignore it, and hope no one notices.

Option 5. DMX - X gon give it to ya.
Fix the bug in webpack and submit a pull request.
 
Last edited:
Drop ie 9/10 support. That traffic makes up a tiny fraction of internet traffic.

Cost vs return, it's not worth it.
 
You have 5 options.

Option 1. 2Pac - Changes
Remove webpack from your build script. But keep babel.

Option 2. Mark Morrison - Return of the Mac.
Check your polyfills and config for webpack/babel, and add any that may be missing... Enable legacy flags etc etc.

Option 3. Snoop Dogg - Drop it like it's hot.
Remove IE9/10 support.

Option 4. Shaggy - Wasn't me.
Ignore it, and hope no one notices.

Option 5. DMX - X gon give it to ya.
Fix the bug in webpack and submit a pull request.

This:crylaugh:
 
You have 5 options.

Option 1. 2Pac - Changes
Remove webpack from your build script. But keep babel.

Option 2. Mark Morrison - Return of the Mac.
Check your polyfills and config for webpack/babel, and add any that may be missing... Enable legacy flags etc etc.

Option 3. Snoop Dogg - Drop it like it's hot.
Remove IE9/10 support.

Option 4. Shaggy - Wasn't me.
Ignore it, and hope no one notices.

Option 5. DMX - X gon give it to ya.
Fix the bug in webpack and submit a pull request.

This is amazing...
 
I think i found the issue, when you use the angular cli to create a project, the version of web-pack-server included doesnt support ie 9/10. If you use an older version of the cli it helps

Drop ie 9/10 support. That traffic makes up a tiny fraction of internet traffic.

Cost vs return, it's not worth it.

Some corporates still use older versions of IE.
 
Top
Sign up to the MyBroadband newsletter
X