-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Configure ForkTsCheckerWebpackPlugin memory limit to avoid crashing #8676
Comments
Does this have anything to do with #8096? |
I'm not sure. I have this issue, and with some dirty manips I succeeded to increase this memory limit without any change with this issue (my build took sometimes more than 12Go before crashing...). But anyway, the capability of define the memoryLimit without doing a fork or touching the code in the node_modules is obviously appreciated. |
@vlatri: They don't specify whether they're using typescript or not in that issue, which matters. If you're not using typescript, everything is done in one process and you can just pass arguments to
But if you're using typescript, you also have to worry about |
I wouldn't like to mess with the |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
This issue has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue. |
@piotr-oles Ok cool so does that mean this issue should stay open or not? |
@nickretallack There is an open PR: TypeStrong/fork-ts-checker-webpack-plugin#404 - this feature is on the list to implement. Currently, I'm working on tests, then I will release an alpha version of 5.0.0. It will be implemented before releasing stable 5.0.0. |
If your typescript code base is large enough,
ForkTsCheckerWebpackPlugin
can hit its memory limit and crash. To increase the memory limit, you have to edit the webpack config. I filed an issue on their repo about this, but they're passing the buck on to you. Can we make this configurable without ejecting?The text was updated successfully, but these errors were encountered: