fix(build): show full error stats#2879
Conversation
501a7ff to
3e85ccb
Compare
|
Thanks for the PR! |
3e85ccb to
f64894f
Compare
|
|
||
| return new Promise((resolve, reject) => { | ||
| webpackCompiler.run((err: any, stats: any) => { | ||
| if (err) { reject(err); } |
There was a problem hiding this comment.
Do we want to return from this?
There was a problem hiding this comment.
I'm not sure it makes any difference. I can return here and on the final resolve/reject one though, what do you think?
f64894f to
13f2be6
Compare
|
this one small, but hides real exception |
|
@valorkin can you clarify what you mean? In the example I gave it seemed to me that the full exception was actually hiding the error a user would need to fix. |
|
I meant that this small fix (by amount of code ) does a great deal. Because previous implementation was hiding real error stack if stats eq null |
|
LGTM |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Currently, running
ng builderror reporting for some classes of errors is not very useful.For example, if you have a reference to an missing styles file in
angular-cli.json, this is the output:This PR makes the error reporting similar to the output of
ng serve, but still maintaining the error exit code: