We generate Webpack builds by hitting one Express route, which triggers a CLI command to build with Webpack. That way, this plugin hangs the process and the route never returns.
I'm pretty sure the problem is with sockets, cause killing the .sock process created by the plugin makes the route respond.
It only happens when we use the route, running the build command on the terminal works. Not using the plugin also works.
We generate Webpack builds by hitting one Express route, which triggers a CLI command to build with Webpack. That way, this plugin hangs the process and the route never returns.
I'm pretty sure the problem is with sockets, cause killing the .sock process created by the plugin makes the route respond.
It only happens when we use the route, running the build command on the terminal works. Not using the plugin also works.