-
-
Notifications
You must be signed in to change notification settings - Fork 597
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
Webpack 5.0.0-beta.22 logs gigantic object to console on error #1726
Comments
I was able to redirect stdout with
Closing this, error messages were just cut off by the long output. |
That's and webpack-cli 3 version in-compatiblity with webpack 5. I think the webpack-cli beta has this fixed. But I think it would be still great to fix it in the stable version. |
OK, thank you Tobias. I got around this but I appreciate your diligence, let me know if you need any additional info to repro. |
Fixed |
Bug report
Title pretty much says it all. Upgraded from webpack 4 to 5.0.0-beta.22 and the build now fails and dumps a huge object to stdout with no additional context. I intend to workaround this, but the logic behind this logging behavior should likely be patched.
What is the current behavior?
The following message is dumped to console, process exits with error code 1:
Expand error
If the current behavior is a bug, please provide the steps to reproduce.
Run
webpack --config
. I'm just bundling some ES modules here, nothing crazy.What is the expected behavior?
A module should build, or I would even settle for a crumb of context in the form of a useful error message.
Other relevant information:
webpack version: 5.0.0-beta.22
Node.js version: v14.5.0
Operating System: Ubuntu 20.04
The text was updated successfully, but these errors were encountered: