12.0.2 Maximum call stack size exceeded
See original GitHub issueExpected Behavior
npm i ngx-cookie-service@12.0.0 --save
npm i; ng build devicewise-angular --prod
successfully build.
Actual Behavior
npm i ngx-cookie-service@latest --save
✖ Compiling TypeScript sources through NGC
ERROR: Maximum call stack size exceeded
An unhandled exception occurred: Maximum call stack size exceeded
Maximum call stack size exceeded when running production build with 12.0.2
.
Steps to Reproduce the Problem
Install ngx-cookie-service@12.0.2
and run ng build --prod
Specifications
- Version: 12.0.2
- Browser: N/A
Issue Analytics
- State:
- Created 2 years ago
- Comments:10
Top Results From Across the Web
JavaScript RangeError: Maximum Call Stack Size Exceeded
The JavaScript RangeError: Maximum call stack size exceeded is an error that occurs when there are too many function calls, or if a...
Read more >Maximum call stack size exceeded on next 11 #30785 - GitHub
Our impression is that something in V8 internals tries to allocate stack memory in some integer proportion to the length of the repeating...
Read more >javascript - Maximum call stack size exceeded error
It means that somewhere in your code, you are calling a function which in turn calls another function and so forth, until you...
Read more >JavaScript Error: Maximum Call Stack Size Exceeded
If you see the “Maximum Call Stack Size Exceeded” error, there's likely a problem with a recursive function within your JavaScript code.
Read more >Random crashes with "Maximum call stack size exceeded"
Go to the node-red folder and try the command npm ls graceful-fs This should show you a dependency tree. When you find out...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I can also confirm from my side, that this issue is resolved. Thanks for taking care of it that quickly!
@pavankjadda the problem was resolved in 12.0.3. Thank you! 🎉