-
Notifications
You must be signed in to change notification settings - Fork 6
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
Does not log in the client's console #4
Comments
It should appear on the Server, the transport is intended to push log information to a centralized collector for logging in a Winston transport. On Mon, Oct 6, 2014 at 3:04 AM, Maxim Zavadskiy [email protected]
|
Right, probably I interpreted this sentence wrong 'logs messages to the console and sends them up to the server as well'. But then which console is mentioned here? |
That is an error. I’ve moved off of using Winston Client in my own projects, but leave this ticket open and I can make some adjustments to properly log on the console in addition to forwarding to the server for collection. On Tue, Oct 7, 2014 at 9:56 AM, Maxim Zavadskiy [email protected]
|
Brent, could you tell, what is the reason you are not using Winston for ur meteor projects? I was looking myself for a framework that allows good logging possibilities with a feature of logging from the client to the server. But there is a lot of options out there, and no official one. |
To be clear, I use Winston on the server, I just don’t use winston-client, which is a transport for Winston, enabling you to push browser logs to the server. On Fri, Oct 10, 2014 at 11:50 AM, Maxim Zavadskiy
|
Any updates on this ticket? For debugging, it's helpful to see logs in the console. |
Using it like
Winston.log( 'info', 'Winston initialized')
does not output anything to the client's consoleThe text was updated successfully, but these errors were encountered: