You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: