-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Need docs for plugin error handling #130
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.
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
Comments
This issue was moved to #101 |
Closing in favor of #37 as plugin error handling should get covered in that doc. |
翻译 guides/code-splitting-libraries;guides/development
So time has moved forward about 2 years and still no answer. Could you please provide a hint on how to report an error from a plugin? |
@EECOLOR If you have access to compilation.warnings.push('warning');
compilation.errors.push('error'); |
Another way would be to throw an error. That would terminate the execution. |
@bebraw Thank you! Exactly what I needed |
From @jasonkuhrt on April 4, 2015 17:8
I am trying to write a plugin for Webpack but unable to find documentation regarding how its error handling is supposed to work. For example if my plugin has a compile error on some file type I presumably should catch it and give it to webpack to present to the user. I cannot find guides or docs about this.
Copied from original issue: webpack/webpack#945
The text was updated successfully, but these errors were encountered: