Webpack.js.org: yarn build --> 100% CPU + RAM usage goes towards its limits

[Legends]

When I try to build the webpack.js.org project I get 100% CPU usage constantly and RAM is rising.
My lap is not the slowest Win10 x64, 16GB RAM and 8 x i7 cores.

git clone https://github.com/webpack/webpack.js.org.git
yarn // install the deps
Open Git Bash --> yarn build   // the build starts

I have to quit the build during execution otherwise my lap gets non-responsive and I do have to do a hard-reboot.

In task manager I can also see several dozens of node.exe processes running, count is rising...

[montogeek]

Yeah, I have a MacbookPro i7, 16 RAM, it takes 25 mins. It is really slow that's why we are doing the Grand rebuild.

What is happening under the hood:
At this moment we use antwar, a Static site generator created by one of the original contributors to this repo, it uses Workers which use all availables cores in your system, basically occupying the entire CPU capacity.

Sorry for the trouble, Did you wanted to make a contribution or something?

[Legends]

No, I didn't want to contribute currently.

But this is not a really clever solution. After 5 builds the lifetime of my CPU`s decreases by 50% haha :D
I mean, if my laptop gets unresponsive, it cannot be good. During the build above I was able to do some screenshots and kill the relevant processes.

Is there an alternative? Or do I have to accept 100% CPU usage when doing yarn build?

P.S.: What is the grand rebuild ?

[montogeek]

@Legends You can change this parameter: https://github.com/webpack/webpack.js.org/blob/master/antwar.config.js#L5

Rebuild: https://github.com/webpack/webpack.js.org/pull/2039

[Legends]

I set it to:
maximumWorkers: 1, but no much success.

After every "Finished writing pages" it again jumps to 100%.

I see it's getting handled, I hope that the grand rebuild takes this issue into account..