-
-
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
Increasing Memory Available to Spawned Instance of Node #2820
Labels
Milestone
Comments
I believe passing flags through to the spawned script makes sense. Can you pull together a PR? |
Will do. Thanks. |
Please make sure this is the default case for npm when running a script which doesn't spawn a sub-porcess; I don't want to create some non-default behavior. |
Right, makes sense. |
This should be resolved by #2913. |
Hi there! This change is out in |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Does it make sense to provide some kind of mechanism to customize the options passed to the spawned Node instance (in
react-scripts.js
)? I'm trying to do something like this:Hacking this file with the above changes makes my build work now without a memory error. But perhaps there is something more generic that could be implemented to give us the ability to pass options into the spawned instance of Node.
Related to #2555.
The text was updated successfully, but these errors were encountered: