Is your feature request related to a problem? Please describe.
Implement api for reporter to allow people choose webpack output.
Describe the solution you'd like
Just add option --reporter [name]/--reporter path/to/reporter.js.
Also have built-in reporters, example standard (maybe best name) and stylish.
Describe alternatives you've considered
Now we have only https://github.com/webpack-contrib/webpack-stylish as plugin. It is bad solution, reporters should be part of webpack-cli.
Additional context
Link on https://github.com/webpack-contrib/webpack-stylish
In near future i will archived webpack-stylish and webpack-command repos to avoid misleading.
Setting this as a high priority. Doing this after new CLI is out. Plan is to use webpack stylish as a default reporter.
Moved to #87
@ev1stensberg Can you please update #87 if this has been moved?
We risk to lose track of what we need to address.
Let's close this is only if completed or the umbrella issue has been updated.
Thanks.
ok
@hulkish has some nice ideas here
@EugeneHlushko can you please provide your input on this? 馃槃
We can combine this with webpack-logger?
This issue had no activity for at least half a year.
It's subject to automatic issue closing if there is no activity in the next 15 days.
Some work on this has been done here
Need to add reporter flag
This is done, we need to add a flag in the CLI to add reporter to the config, other than that, we're jazz 馃幖
This is done, we need to add a flag in the CLI to add reporter to the config, other than that, we're jazz 馃幖
@evenstensberg how are taking forward given that we have a reporter added. I can pick up if you provide a little bit of guidance.
Add the plugin if the flag is present, that's it
@evenstensberg can you elaborate please?
So to add this feature you will need to:
1) Check if a flag named --output-reporter is present
2) If so, add the reporter plugin to a configuration
You will need to add the flag to cli-flags.js
@evenstensberg I will work on this one.
If so, add the reporter plugin to a configuration
can anyone provide me the link to the reporter plugin?
It's not listed here https://webpack.js.org/plugins/
@snitin315 This is probably the plugin you are looking for https://github.com/misterdev/webpack-reporter-plugin
This issue had no activity for at least half a year.
It's subject to automatic issue closing if there is no activity in the next 15 days.
wtf, how is this highly requested feature being closed
Fixed for webpack@5, you can use hooks to customize stats output, example of default plugin https://github.com/webpack/webpack/blob/master/lib/stats/DefaultStatsPrinterPlugin.js, also stats was refactored for webpack@5 and looks good, anyway if you have ideas how we can improve it better, please open an issue in webpack repo
I arrived here from the webpack-stylish repo, which was deprecated as the reporter was added to the cli.
But I can't find how to enable it :smile:
How do I get the same as the stylish plugin:

@alexander-akait there is no documentation at all on how to use the DefaultStatsPrinterPlugin.
The webpack output is nowhere near the webpack-stylish one, and there is no documentation on how to achieve what users like @lonix1 want.
@marcofugaro default webpack v5 output is like stylish, why do you need modify output
This does not look anything like the stylish screenshot a couple of comments above.

Please provide a way for users to get that kind of output as it was in webpack-stylish.
It is improve stylish - assets with size + flags + entry points + version and time
I fail to see how the new report is better than the old report, but maybe it's just me! :smile:
@marcofugaro or anyone else: Do you know how to get a pretty report like before?
but maybe it's just me!
It's not just you.
Do you know how to get a pretty report like before?
You have to disable the default webpack output with stats: false and then you have to do your custom logging relying on the hooks exposed by the event-hooks-webpack-plugin.
You have to disable the default webpack output with
stats: falseand then you have to do your custom logging relying on the hooks exposed by the event-hooks-webpack-plugin
So basically: reinvent the wheel or use the new report ;-)
Most helpful comment
Setting this as a high priority. Doing this after new CLI is out. Plan is to use webpack stylish as a default reporter.