--prod does not work in Firefox ESR 45.9.0

[jmajnek]

Hi,

running ´ng serve --prod´ and opening the application in Firefox ESR 45.9.0 throws an exception.

TypeError: this is undefined

Versions

ng: 1.6.5
npm: 5.6.0
Node: 8.9.4

Repro steps

• ng new foobar
• cd foobar
• ng serve --prod
• Open in Firefox ESR 45.9.0

Observed behavior

Blank page, error in console

Desired behavior

Everything works as expected

BR
Jakob

[matthiaslischka]

I can reproduce this with Firefox 45.9.0 ESR win 32. Get it here.
BR

[hansl]

error in console

Could you be more specific?

[matthiaslischka]

There is not much more to it. One Warning and one error that this is undefinded

[Warning] mutating the [[Prototype]] of an object will cause your code to run very slowly; instead create the object with the correct initial [[Prototype]] value using Object.create 
  main.0836c96b9484632bf48c.bundle.js:1:10588
[Error] TypeError: this is undefined   main.0836c96b9484632bf48c.bundle.js:1:87832

It works just fine with any other browser or when you do not add the --prod flag.

BR

[wunaidage]

same here, exactly the same behavior and console output

[TheParad0X]

Same problem here with Firefox 50.1.0. See #9362
Current workaround: instead of using
ng build --prod
use
ng build --aot --environment=prod --output-hashing=all --sourcemaps=false --extract-css=true --named-chunks=false --build-optimizer=true

The culprit is --target=production

[nstod]

We are seeing the same issue. The workaround submitted by @TheParad0X does indeed work, but it appears to bypass uglify, which we would greatly desire. I'm hoping to see this fixed as soon as possible.

[pfeigl]

We are facing the same problem and leaving the production flag out is no real option, because the dist size is not an option than (because of the missing uglify process).

Also all code is effectively visible to everyone way to easily (which might be a problem to closed-source projects)

[nstod]

We found a temporary workaround by reverting uglifyjs-webpack-plugin from version 1.1.8 to 1.1.5. Uglify is once again working on Firefox 45 for us.

[wunaidage]

#8997 see this issue, will reverting uglifyjs cause this issue again?