perf: do not spawn new process for running webpack

[anshumanv]

What kind of change does this PR introduce?

fix

Did you add tests for your changes?
Not yet

If relevant, did you update the documentation?
No

Summary
Do not spawn new process for running the CLI

Does this PR introduce a breaking change?
Shouldn't

Other information

[alexander-akait]

Do you need help with tests?

[snitin315]

Yes, I'm helping with the node flags support. I will push changes soon.

[snitin315]

Using NODE_OPTIONS gives desired behavior with webpack@next only and valid node flags but if we use invalid node flags it throws the following error -

[alexander-akait]

I think we should remove --node-args in favor NODE_OPTIONS, because all tools uses NODE_OPTIONS, no one implement --node-args

[anshumanv]

I think we should remove --node-args in favor NODE_OPTIONS, because all tools uses NODE_OPTIONS, no one implement --node-args

Yeah we can remove, also doing unnecessary parsing

[alexander-akait]

Let's do it here 👍

[anshumanv]

Okay, on it

[alexander-akait]

Here we improve starting webpack around 50-200ms on different computers (already tested), it is very good improvements

[anshumanv]

Here we improve starting webpack around 50-200ms on difference computer (already tested), it is very good improvements

Thanks for the benchmark!

[anshumanv]

CI freeze 😞

[alexander-akait]

Great work!

[alexander-akait]

/cc @webpack/cli-team need review

[snitin315]

💯

[anshumanv]

Something wrong with commitlint 😞

[alexander-akait]

@anshumanv Don't worry about commitlint I will fix commit message before merge, anyway we need look why it is broken