-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(core): use concat in buildAllWorkspaceFiles to avoid Maximum call stack size exceeded #18065
Conversation
… stack size exceeded
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit b44823c. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
Thanks for the PR! I seen someone complain about this before, but they didn't give me much info, and the problem was fixed for them when they used a different version of Node. Is the Nx workspace that gave you this error open source or available for me to use as a benchmark? |
@Cammisuli It's a private repo, so I can't share with you. Sorry for that. |
@chentsulin can I get some details on the workspace? How many projects do you have, and how many global files were there as well? |
@Cammisuli AFAICT, we have more than 100 packages and 30 Next.js websites. |
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Use
.concat
instead of.push(...arr)
to avoidMaximum call stack size exceeded
.Current Behavior
Got this error in an large monorepo:
Expected Behavior
Do not throw
RangeError: Maximum call stack size exceeded
Related Issue(s)
Fixes #