Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
RangeError: Maximum call stack size exceeded
See original GitHub issueDescribe the problem
update cli/core/material to 9.1/9.2 version (global cli 9.1, node 13.9) and got errors while serve app:
`Error: Error when flattening the source-map “…/app/node_modules/@fortawesome/angular-fontawesome/config.d.ts.map” for “…/app/node_modules/@fortawesome/angular-fontawesome/config.d.ts”: RangeError: Maximum call stack size exceeded
Error: Error when flattening the source-map “…/app/node_modules/@fortawesome/angular-fontawesome/icon-library.d.ts.map” for “…/app/node_modules/@fortawesome/angular-fontawesome/icon-library.d.ts”: RangeError: Maximum call stack size exceeded
Error: Error when flattening the source-map “…/app/node_modules/@fortawesome/angular-fontawesome/stack/stack-item-size.directive.d.ts.map” for “…/app/node_modules/@fortawesome/angular-fontawesome/stack/stack-item-size.directive.d.ts”: RangeError: Maximum call stack size exceeded
Error: Error when flattening the source-map “…/app/node_modules/@fortawesome/angular-fontawesome/icon/icon.component.d.ts.map” for “…/app/node_modules/@fortawesome/angular-fontawesome/icon/icon.component.d.ts”: RangeError: Maximum call stack size exceeded
Error: Error when flattening the source-map “…/app/node_modules/@fortawesome/angular-fontawesome/icon/duotone-icon.component.d.ts.map” for “…/app/node_modules/@fortawesome/angular-fontawesome/icon/duotone-icon.component.d.ts”: RangeError: Maximum call stack size exceeded
Error: Error when flattening the source-map “…/app/node_modules/@fortawesome/angular-fontawesome/layers/layers.component.d.ts.map” for “…/app/node_modules/@fortawesome/angular-fontawesome/layers/layers.component.d.ts”: RangeError: Maximum call stack size exceeded
Error: Error when flattening the source-map “…/app/node_modules/@fortawesome/angular-fontawesome/layers/layers-counter.component.d.ts.map” for “…/app/node_modules/@fortawesome/angular-fontawesome/layers/layers-counter.component.d.ts”: RangeError: Maximum call stack size exceeded
Error: Error when flattening the source-map “…/app/node_modules/@fortawesome/angular-fontawesome/layers/layers-text.component.d.ts.map” for “…/app/node_modules/@fortawesome/angular-fontawesome/layers/layers-text.component.d.ts”: RangeError: Maximum call stack size exceeded
Error: Error when flattening the source-map “…/app/node_modules/@fortawesome/angular-fontawesome/stack/stack.component.d.ts.map” for “…/app/node_modules/@fortawesome/angular-fontawesome/stack/stack.component.d.ts”: RangeError: Maximum call stack size exceeded
Error: Error when flattening the source-map “…/app/node_modules/@fortawesome/angular-fontawesome/fontawesome.module.d.ts.map” for “…/app/node_modules/@fortawesome/angular-fontawesome/fontawesome.module.d.ts”: RangeError: Maximum call stack size exceeded
Error: Error when flattening the source-map “…/app/node_modules/@fortawesome/angular-fontawesome/angular-fontawesome.d.ts.map” for “…/app/node_modules/@fortawesome/angular-fontawesome/angular-fontawesome.d.ts”: RangeError: Maximum call stack size exceeded`
What did you expect?
serve without errors
Reproducible test case
just update from v9 to v 9.1 and serve project (TSLint v 6.1)
Issue Analytics
- State:
- Created 3 years ago
- Comments:8
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Manually removing the node_modules folder and installing again has worked for me. I have no errors now. Thanks again
I’m going to close this issue as there is nothing to fix on the
@fortawesome/angular-fontawesomeside. If you still experience it and have a reproduction, open new issue on the Angular issue tracker, so they can fix it. Otherwise refer to https://github.com/angular/angular/issues/35757 for a set of workarounds.