-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Option to console.log only important stuff #109
Comments
+1 |
I agree the following are not useful logs and they are cluttering up my console making it more difficult to sort through and find my own logs.
There should be some way for me to disable these logs. This same issue was filed on the react-hot-loader, but it is apparently a webpack issue (gaearon/react-hot-loader#79). |
+1 |
Would like this option as well. The logs are a bit verbose after everything is setup correctly. |
👍 |
+1 as well |
As a very messy temporary work around, I have a script,
It overloads |
Previously, when you used `quiet: true` or `noInfo: true` via the Node API or CLI, this only had effect on the output in the terminal (issue #109). With this PR, these settings will be respected in the browser console as well. Maybe it would be more flexible to add a separate option for this, but this would also mean more configuration. Looking for feedback on this.
Previously, when you used `quiet: true` or `noInfo: true` via the Node API or CLI, this only had effect on the output in the terminal (issue #109). With this PR, these settings will be respected in the browser console as well. Maybe it would be more flexible to add a separate option for this, but this would also mean more configuration. Looking for feedback on this.
Can you guys check if PR #579 works for you? Looking for feedback! |
PR #579 was merged, check that out for more info. Note that it hasn't been released yet. |
Released in |
Thanks for this @SpaceK33z |
Hi
I narrowed it down to realize it only happens when I have Any idea? |
Same issue, still see the logs with |
Thought it was bad form to leave console.log() lines in your production code... |
It is planned or should I send PR?
We don't care about these messages:
There should be an option (default) to log only warnings and errors.
The text was updated successfully, but these errors were encountered: