Webpack stucks and keep spawning hundreds of nodejs processes

Do you want to request a feature or report a bug?

What is the current behavior?
Webpack is stuck when running the command and keep spawning nodejs processes.
The nodejs processes can up to 300 processes or even more, until I force stop it by using Ctrl+C.

The commands I mentioned above are:
webpack --mode development
webpack --mode production
or other basic commands.

I tried to run webpack --mode developmenta , but webpack doesn’t tell me typo on developmenta. It keeps stuck and spawing bunch of nodejs processes.

If the current behavior is a bug, please provide the steps to reproduce.
To reproduce, I just run the basic command as I told above.

What is the expected behavior?
The webpack bundles my scripts as usual.

Please mention other relevant information such as the browser version, Node.js version, webpack version, and Operating System.
node: 9.3.0
webpack: 4.2.0
webpack-cli: 2.0.12

I don’t know what happened, but yesterday, my webpack is running as usual, nothing weird. But today, it happens to all of my projects.
Is it related to cache problems?

There is only one directory affected to this problem. The directory itself is just normal directory (no node_modules, package.json, git, etc.) with several projects located inside.

Author: Fantashit

1 thought on “Webpack stucks and keep spawning hundreds of nodejs processes

Comments are closed.