Replies: 2 comments
-
Ah yes, I think I once tried to move all to stdout but I never completed my work. What do you think, @th0r? Should we move all debug and warning/error logs to STDERR so that piping commands works in *nix? |
Beta Was this translation helpful? Give feedback.
0 replies
-
I don't think using |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The plugin appears to send all its logs to STDOUT rather than STDERR (ie. as it would using
console.error
). This breakswebpack --json > stats.json
. Is there any support for changing the log messages to STDERR?Technical info
Debug info
How do you use this module? As CLI utility or as plugin? As a plugin
If CLI, what command was used? (e.g.
webpack-bundle-analyzer -O path/to/stats.json
)If plugin, what options were provided? (e.g.
new BundleAnalyzerPlugin({ analyzerMode: 'disabled', generateStatsFile: true })
)What other Webpack plugins were used? None
Beta Was this translation helpful? Give feedback.
All reactions