You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing a custom web element library (specifically @microsoft/fast-components) through node with the custom elements schema enabled, the custom web elements render fine in development mode. However, when building the application in the default "production" configuration with buildOptimizer set to true, the custom elements will cause a "call stack size exceeded" error. This error does not happen normally on these elements.
🔬 Minimal Reproduction
Pull the repro from here. This is a base Angular 11 project with @microsoft/fast-components installed. The components are included as instructed on this site.
Normal behavior:
Pull the repo
Run npm i
Run npm start
Open localhost:4200
See a simple textbox and radio button rendered and no console errors
Reproduce error:
Run npm start-prod
Open localhost:5005
Observe the console error and the radio button un-rendered
If buildOptimizer in angular.json for the production mode is set to false the error will not occur for npm start-prod.
🔥 Exception or Error
polyfills-es2015.1f913f16a2d346cc8bdc.js:1 Uncaught RangeError: Maximum call stack size exceeded
at mi.watch (main-es2015.1dde2514dd0a5acad672.js:1)
at ai.getValue (main-es2015.1dde2514dd0a5acad672.js:1)
at HTMLElement.get [as checked] (main-es2015.1dde2514dd0a5acad672.js:1)
at mi.watch (main-es2015.1dde2514dd0a5acad672.js:1)
at ai.getValue (main-es2015.1dde2514dd0a5acad672.js:1)
at HTMLElement.get [as checked] (main-es2015.1dde2514dd0a5acad672.js:1)
at mi.watch (main-es2015.1dde2514dd0a5acad672.js:1)
at ai.getValue (main-es2015.1dde2514dd0a5acad672.js:1)
at HTMLElement.get [as checked] (main-es2015.1dde2514dd0a5acad672.js:1)
at mi.watch (main-es2015.1dde2514dd0a5acad672.js:1)
main-es2015.1dde2514dd0a5acad672.js:1 ERROR RangeError: Maximum call stack size exceeded
at getNotifier (main-es2015.1dde2514dd0a5acad672.js:1)
at mi.watch (main-es2015.1dde2514dd0a5acad672.js:1)
at ai.getValue (main-es2015.1dde2514dd0a5acad672.js:1)
at HTMLElement.get [as checked] (main-es2015.1dde2514dd0a5acad672.js:1)
at mi.watch (main-es2015.1dde2514dd0a5acad672.js:1)
at ai.getValue (main-es2015.1dde2514dd0a5acad672.js:1)
at HTMLElement.get [as checked] (main-es2015.1dde2514dd0a5acad672.js:1)
at mi.watch (main-es2015.1dde2514dd0a5acad672.js:1)
at ai.getValue (main-es2015.1dde2514dd0a5acad672.js:1)
at HTMLElement.get [as checked] (main-es2015.1dde2514dd0a5acad672.js:1)
un @ main-es2015.1dde2514dd0a5acad672.js:1
🐞 bug report
Affected Package
This issue is caused by @angular/compiler
Is this a regression?
This did not work as far back as v. 9.
Description
When installing a custom web element library (specifically @microsoft/fast-components) through node with the custom elements schema enabled, the custom web elements render fine in development mode. However, when building the application in the default "production" configuration with
buildOptimizer
set to true, the custom elements will cause a "call stack size exceeded" error. This error does not happen normally on these elements.🔬 Minimal Reproduction
Pull the repro from here. This is a base Angular 11 project with @microsoft/fast-components installed. The components are included as instructed on this site.
Normal behavior:
npm i
npm start
Reproduce error:
npm start-prod
If
buildOptimizer
in angular.json for the production mode is set tofalse
the error will not occur fornpm start-prod
.🔥 Exception or Error
🌍 Your Environment
Angular Version:
The text was updated successfully, but these errors were encountered: