Angular production builds with script optimizations cause recursion RangeError

[rajsite]

The optimization pass for scripts introduces an error at runtime in production builds. Temporarily disable script optimizations until fixed. Optimizations in the production build of the example-client-app were disabled in: d67778a

Example stack:

Uncaught RangeError: Maximum call stack size exceeded
    at va.has (main.e90fa8c4bcbabc2a18ca.js:1)
    at va.subscribe (main.e90fa8c4bcbabc2a18ca.js:1)
    at wa.subscribe (main.e90fa8c4bcbabc2a18ca.js:1)
    at $a.watch (main.e90fa8c4bcbabc2a18ca.js:1)
    at Ta.getValue (main.e90fa8c4bcbabc2a18ca.js:1)
    at e.get [as _rawValue] (main.e90fa8c4bcbabc2a18ca.js:1)
    at e.get rawValue [as rawValue] (main.e90fa8c4bcbabc2a18ca.js:77)
    at e.resolveRawValue (main.e90fa8c4bcbabc2a18ca.js:77)
    at e.resolveRealValue (main.e90fa8c4bcbabc2a18ca.js:77)
    at e.get value [as value] (main.e90fa8c4bcbabc2a18ca.js:77)

[rajsite]

Looks related to this issue: angular/angular-cli#11439 (comment)
Similar to others, disabling the unsafe pure_getters option manually has very little change on bundle size (271.52 kB broken and 272.34kB running). Unfortunate that Angular is not allowing an option for disabling unsafe transforms.

[rajsite]

Disabling build optimizer seems to work: amcharts/amcharts4#1146 (comment)
Results in a dist size of 456.51kB 😢

[rajsite]

Looks like we need the custom optimization levels feature: angular/angular-cli#15761
Another project that had the exact same issue with fast-elements and angular: angular/angular-cli#19705
Issue that sounds the same in fast-element: microsoft/fast#4793