-
Notifications
You must be signed in to change notification settings - Fork 11
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
Logging #70
Comments
So, I was tinkering with the generate-auto config command last night, and I think we need to give a bit more thought about how Bunyan is going to be used. I'm all for using a more sophisticated logging architrcture, as I'd like to eventually pipe all my logs to a Splunk server. The problem is that people aren't necessarily guaranteed to have bunyan installed (or eslint for that matter). So I think we need to give some thought as to how those other tools get installed and configured before we migrate the entire app to using bunyan. |
". . . aren't necessarily guaranteed to have bunyan installed . . . " Sorry but, are you concerned about the need for the Bunyan command line filter OR about adding bunyan to your package,json file? Either way, I'm not clear on the extent of the repercussions you anticipate. |
As per Martin:
Logging
With Bunyan or Winston, it is very beneficial and mercifully easy to not use console. (You might want to skim this comparison.) Please see these pages :
If you want to review my changes to
generate_autoconfig.js
you will need to run :The text was updated successfully, but these errors were encountered: