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
After adding to a transport that it should handle an exception (with 'handleExceptions: true') and throwing an unhandled error, every log which should be logged does not get logged at all in that same transport which handled the exception. No info logging or error logging or anything in between .
What version of Winston presents the issue?
v3.13.0
What version of Node are you using?
v16.20.2
If this worked in a previous version of Winston, which was it?
Other transports still work fine after the exception was thrown. Only the transport which handled the exception doesn't log anymore. In my case it should'nt stop logging, I want the application to continue even when an exception occurs.
The text was updated successfully, but these errors were encountered:
馃攷 Search Terms
handleException
The problem
After adding to a transport that it should handle an exception (with 'handleExceptions: true') and throwing an unhandled error, every log which should be logged does not get logged at all in that same transport which handled the exception. No info logging or error logging or anything in between .
What version of Winston presents the issue?
v3.13.0
What version of Node are you using?
v16.20.2
If this worked in a previous version of Winston, which was it?
No response
Minimum Working Example
In the code I throw an example error with:
Additional information
Other transports still work fine after the exception was thrown. Only the transport which handled the exception doesn't log anymore. In my case it should'nt stop logging, I want the application to continue even when an exception occurs.
The text was updated successfully, but these errors were encountered: