Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reason for error handling change introduced in v0.4.6? #43

Open
cappadona opened this issue Apr 28, 2017 · 0 comments
Open

Reason for error handling change introduced in v0.4.6? #43

cappadona opened this issue Apr 28, 2017 · 0 comments

Comments

@cappadona
Copy link

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cappadona