question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Output logging is too verbose and can't be disabled or minimized

See original GitHub issue

After enabling this plugin on our project, our webpack build now spits out hundreds of pages of mini-css-extract-plugin output, none of which is particularly helpful or informative. I see thousands of lines like this:

Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/postcss-loader/src/index.js??ref--11-2!node_modules/less-loader/dist/cjs.js??ref--11-3!webpack/color-sharing-loader.js!<redacted>:
    Entrypoint mini-css-extract-plugin = *
       2 modules

Is there a way to disable or minimize all these messages? Our CI logs are now full of them and all this extra noise makes legitimate errors harder to find.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:16 (5 by maintainers)

github_iconTop GitHub Comments

3reactions
kaiyomacommented, Feb 5, 2020

@lensbart stats output creates webpack + webpack-cli, we are not doing anything special, this is not even an error, you can setup the output using the stats option in your configuration. Tell me how you want to fix it? We display all the data necessary for analysis, you can set stats: "errors-warnings" to avoid extra output in develement env

This is not a good solution. I tried this out locally and I noticed that some very helpful webpack output is now being suppressed (specifically, the display of assets, file sizes, and chunks).

The correct solution, which someone else mentioned already (in the other issue), is that the messages from this plugin should be logged at the verbose level. That way, they’re suppressed during normal operation, but users can view them if they really want to. I’m pretty sure that will solve the issue here and make everyone happy.

1reaction
bhjcommented, Aug 22, 2020

Thanks, I believe so, though in this case webpack-dev-middleware is involved (via koa-webpack) so I’m trying app.use(middleware, { devMiddleware: { stats: { children: false } } }) in place of this line, and still no change 🤷

That other thread did make a good case for why children: false isn’t a great long-term solution, so hopefully the “simplified output” with webpack@5 will be enough until I can track this down. Thanks again for taking a look!

Read more comments on GitHub >

github_iconTop Results From Across the Web

How can I make ffmpeg be quieter/less verbose? - Super User
I've tried -loglevel quiet -- still not quiet. I should mention, I'm looking for "quieter," not "no output ever". If there's an error...
Read more >
How to enable global and advanced logging for Microsoft ...
Describes how to enable global and advanced logging for Outlook 2010, Outlook 2013, and Outlook 2016.
Read more >
How to suppress verbose Tensorflow logging? - Stack Overflow
I'm unittesting my Tensorflow code with nosetests but it produces such amount of verbose output that makes it useless. The following test import...
Read more >
Logging and Log Levels
Trace and. Verbose log levels track and write the values of input/output arguments in Orchestrator logs. If those values include PII information, they...
Read more >
Python Logging Guide - Best Practices and Hands-on Examples
Formatters specify the layout of log records in the final output. ... First, open files using blocks, so you won't have to worry...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found