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
hi, one of the reasons to use winston is because it supports logging both in node.js and in frontend javascript code.
for teams like us that package javascript code in a shared library that may run in both front-end javascript and back-end node.js, this transport library doesn't work - when we boot up our front-end page we get this -
since winston explicitly supports logging in both front-end and back-end components, this library should either work in the front-end or explicitly say that it doesn't support browser environments.
if it doesn't support browser environments, then we are probably going to have to move to a different logging service other than Sentry
The text was updated successfully, but these errors were encountered:
hi, one of the reasons to use winston is because it supports logging both in node.js and in frontend javascript code.
for teams like us that package javascript code in a shared library that may run in both front-end javascript and back-end node.js, this transport library doesn't work - when we boot up our front-end page we get this -
since winston explicitly supports logging in both front-end and back-end components, this library should either work in the front-end or explicitly say that it doesn't support browser environments.
if it doesn't support browser environments, then we are probably going to have to move to a different logging service other than Sentry
The text was updated successfully, but these errors were encountered: