-
Notifications
You must be signed in to change notification settings - Fork 16.6k
fix(build): Increase ForkTsCheckerWebpackPlugin memory limit to fix OOM error #37583
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
Conversation
Code Review Agent Run #058487Actionable Suggestions - 0Review Details
Bito Usage GuideCommands Type the following command in the pull request comment and save the comment.
Refer to the documentation for additional commands. Configuration This repository uses Documentation & Help |
sadpandajoe
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this. I think for my fork i just removed the check but this is the correct fix.
EnxDev
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Code Review Agent Run #e088e0Actionable Suggestions - 0Review Details
Bito Usage GuideCommands Type the following command in the pull request comment and save the comment.
Refer to the documentation for additional commands. Configuration This repository uses Documentation & Help |
SUMMARY
Increases the memoryLimit for
ForkTsCheckerWebpackPluginfrom 4096 MB to 8192 MB to fix JavaScript heap out of memory errors during production builds.The TypeScript type checker runs in a forked child process with its own memory limit separate from the main webpack process. While the main webpack process already has 8GB allocated via
NODE_OPTIONS=--max_old_space_size=8192, the forked TypeScript checker was limited to 4GB, which is insufficient for the current codebase size (~14,000 modules).BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
Before: Build fails with FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
After: Build completes successfully
ADDITIONAL INFORMATION