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
"Pretty" error rendering fails, hiding the original error #921
Comments
Thanks for reporting - that sounds quite aweful. |
Unfortunately I'm having trouble reproducing it locally. If I replace pngquant with a script that emits the above error it works. It may be environment specific on our CI server. |
Any updates on reproduction? |
Nope, sorry. It could be worth wrapping the call to |
Okay sounds good - Could you please open a pull request? |
Sure: #925 |
Cool ty 👍 |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
I've been occasionally getting an error on our circle ci build that looks like below. It appears that there is an error in the error reporting code which means I can't see what the actual error is. I was able to reproduce it on the server and see what the actual error was, so that's good, but it'd be great if html-webpack-plugin didn't use pretty error rendering (or at least fell back to a straight up
console.log
if it failed).In case it helps, I included the actual error below.
Error Message & Stack Trace
Actual error:
Environment
Tell us which operating system you are using, as well as which versions of Node.js, npm, webpack, and html-webpack-plugin. Run the following to get it quickly:
The text was updated successfully, but these errors were encountered: