-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
Aggregate errors or errors with cause are not logged #17836
Comments
I seem to have the same problem. I tried the following in NestJS with
In the terminal I see that the cause is not logged:
When I run
The webpack version that is used by nest cli is 5.90.1. |
Feel free to send a PR |
In my case it seems it's not webpack, my error is logged somewhere else in Nest. |
@steverep could you send a minimum code that could reproduce this error? |
Bug report
What is the current behavior?
If an
AggregateError
orError
withcause
is thrown, Webpack intercepts and only logs the primary message. For these cases, that message is often just an annotation on the real error, making it impossible to debug them from a Webpack plugin.If the current behavior is a bug, please provide the steps to reproduce.
Throw an instance of
AggregateError
or an instance ofError
with acause
property from any plugin, and then just examine the console output.What is the expected behavior?
AggregateError
, each of theerrors
should be loggedError
withcause
, thecause
should be logged as wellOther relevant information:
webpack version: 5.89.0
Node.js version: 20
Operating System: Linux
Additional tools:
The text was updated successfully, but these errors were encountered: