You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case of meteor, farpoint/meteor-winston-client can be used for logging within client folder and tomrogers3/meteor-winston can be used for logging within the server folder.
But what about the code that is placed in common folders, i.e. any folder except client and server?
SO in meteor, what ever is placed in client folder is deployed on client side and what ever is placed in server folder is deployed on server side. But what ever is placed in any other folder is deployed on both client and server side. So this question is about those common folders.
The text was updated successfully, but these errors were encountered:
meghadev
changed the title
In meteor, what about the common logs
In meteor, what about the logs in common folders?
Feb 26, 2016
Good question - this package was designed to scratch my own itch, as it were. A general-purpose Winston-like logger that includes routing from client to server to log transport would be ideal in this case. I have not been maintaining this package due to a lack of need to see those logs from the clients at this point, however pull requests are welcome!
In case of meteor, farpoint/meteor-winston-client can be used for logging within client folder and tomrogers3/meteor-winston can be used for logging within the server folder.
But what about the code that is placed in common folders, i.e. any folder except client and server?
SO in meteor, what ever is placed in client folder is deployed on client side and what ever is placed in server folder is deployed on server side. But what ever is placed in any other folder is deployed on both client and server side. So this question is about those common folders.
The text was updated successfully, but these errors were encountered: