-
-
Notifications
You must be signed in to change notification settings - Fork 603
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
[Feature]: Increase memory with a flag / Support Node Flags #289
Comments
I'm down to grab this, but i'm not really sure where do i add the flags. webpack-cli/bin/convert-argv.js Line 29 in 8787043
|
@playma256 No, it is part of the process args, not process environment variables |
You could do something like |
I expressed myself in a wrong way, sorry for that. I'm grabbing this issue. |
I was having a look how to implement those flags, and i've reached a fork road. I'm not able to override node flag options when a process already started, so i was thinking... spawning a child process passing down v8 flags would be a cumbersome idea or is there a way (i actually dont know any...) to update v8 flags when a process already started? What do you all think? Edit |
Getting back to you on this. This might not be possible without invoking |
is there a way to run a single test only? A single binary test? |
Not at the moment :( |
This impl can be used with #15 . We keep track of pId and restart a process once it's done ( I think ) |
This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days. |
Can npx used to accomplish the result? i.e: |
Yes if npm supports injection of args. We cannot use this as a fix to us, as the flags needs to be supported by default not by running npx |
This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days. |
Could
webpack-cli
handle the memory limit increase with a flag?Right now we have to manually use:
node --max_old_space_size=4096 node_modules/webpack/bin/webpack.js
A simple flag would be very nice instead:
webpack --increase-memory 4096
Or multiple custom node options like:
webpack --node.increase-memory 4096 --node.trace-deprecation --node.experimental-modules
The text was updated successfully, but these errors were encountered: