Stuck on an issue?
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.
regex throws Maximum call stack size exceeded error
See original GitHub issueHello.
We recently did a npm update on our project to find that suddenly Webpack had stopped working. After investigating the culprit is this commit https://github.com/postcss/postcss/commit/54cbf3c4847eb0fb1501b9d2337465439e849734 in postcss.
It changes the regex and this creates an error with big files.
Issue Analytics
- State:
- Created 2 years ago
- Comments:20 (10 by maintainers)
Top Results From Across the Web
JS Regex throwing Maximum call stack size exceeded error
"Maximum call stack size exceeded" tells you, that there are too many stored execution contexts (= function calls) - which most likely happens ......
Read more >How to fix: "RangeError: Maximum call stack size exceeded"
A "RangeError: Maximum call stack size exceeded" is an error that occurs when a function or operation tries to execute too many nested...
Read more >JavaScript RangeError: Maximum Call Stack Size Exceeded
The RangeError: Maximum call stack size exceeded is thrown when a function call is made that exceeds the call stack size. This can...
Read more >Avoid Maximum call stack size exceeded in JavaScript
Overview · Error Maximum call stack size exceeded is raised when calling a recursive function in a loop · This is expected –...
Read more >Uncaught RangeError: Maximum call stack size exceeded
Moreover, you can managed to find the point that was causing the error by check the error details in the Chrome dev toolbar...
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 Free
Top 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
The fix was released in 8.3.10.
@yetingli I changed your suggestion from https://github.com/postcss/postcss/pull/1647 164eb37 Can you check that it doesn’t have security issues?
@AlexisFinn can you open
node_modules/postcss/lib/previous-map.js, replace content with file from GitHub’smainand check that it fixed the problem?