I'm trying to understand the reasoning behind 170c250 which was introduced in v0.4.6.
Prior to this change, the plugin would pass an error on to Webpack, but as a result of this change any error from a shell command now kills the Webpack process. Is this the desired/expected behavior or a bug?
This could be related to #38
I'm trying to understand the reasoning behind 170c250 which was introduced in
v0.4.6.Prior to this change, the plugin would pass an error on to Webpack, but as a result of this change any error from a shell command now kills the Webpack process. Is this the desired/expected behavior or a bug?