Skip to content
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

[idea] Silencing Webpack output #1719

Closed
2 of 6 tasks
drawcard opened this issue Sep 16, 2016 · 6 comments
Closed
2 of 6 tasks

[idea] Silencing Webpack output #1719

drawcard opened this issue Sep 16, 2016 · 6 comments

Comments

@drawcard
Copy link
Contributor

Submit a feature request or bug report

Feature Request

(delete this section if not applicable)

Please provide use cases for changing the current behavior:

Currently, Webpack spits out a heap of information when running 'npm start' and it's a bit overwhelming, especially as asset counts grow for a project. Plus, BrowserSync connection information gets lots in the mix. I would like to propose building in the option to disable the superfluous information (maybe making it a default, and toggling it off if desired.)

Other relevant information:

Ideas for implementing this can be found here: http://stackoverflow.com/a/31933551

This solution is ideal as it allows error messages to pass through, while suppressing everything else.

@derkjn
Copy link
Contributor

derkjn commented Sep 16, 2016

I had a play around the current configuration files and turns out, this would be extremely easy.
Following the stackoverflow post, I simply added {noInfo: true} to the current webpack.plugin.browsersync.js middleware function.
Don't know if this will get approved for sage or not but definitely nice to have a cleaner output!

@drawcard
Copy link
Contributor Author

Cool. I thought it would be pretty simple to do. Might be worthy of a PR!

@mrobit
Copy link

mrobit commented Oct 18, 2016

Webpack output in the command line can get ridiculous, especially if you cmd+click on the URL browser-sync outputs in the terminal when the server command is started. +1 from me.

@drawcard
Copy link
Contributor Author

It's especially a pain when you're trying to catch an error in a SCSS file for example, but it all whizzes past too quickly to read it in the console.

I've found a better solution that just supresses the chunk information, but still gives you useful stats on the watched files. It also still outputs errors and warnings, eg deprecation messages from SASS. It's not as noisy as before but it's still useful. I'm about to submit a PR with the change 👍

image

@retlehs
Copy link
Member

retlehs commented Nov 17, 2016

closed by #1751

@retlehs retlehs closed this as completed Nov 17, 2016
@drawcard
Copy link
Contributor Author

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants