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
I'm the author of the winston-log-and-exit, and have some users of this package have complained that this package doesn't work with winston-log-and-exit. As you may know, cleanly exiting a process and retaining the last few log entries is a perennial problem for winston users, which is confounded by poor documentation on how Winston identifies streaming loggers, and what API streaming loggers should implement.
In short, to work with winston-log-and-exit a custom Streaming Transport needs a ._stream attribute, has an .end() method, and which issues a "finish" event when all the messages that were logged before the .end() method was called.
Cheers,
-Jason
The text was updated successfully, but these errors were encountered:
hi @jdthorpe - i'm no longer using this package (no longer using rsyslog for logs), so if you'd like to add a patch, let me know and i'll add you as a collaborator.
Hello,
I'm the author of the winston-log-and-exit, and have some users of this package have complained that this package doesn't work with
winston-log-and-exit
. As you may know, cleanly exiting a process and retaining the last few log entries is a perennial problem for winston users, which is confounded by poor documentation on how Winston identifies streaming loggers, and what API streaming loggers should implement.In short, to work with
winston-log-and-exit
a custom Streaming Transport needs a._stream
attribute, has an.end()
method, and which issues a "finish" event when all the messages that were logged before the.end()
method was called.Cheers,
-Jason
The text was updated successfully, but these errors were encountered: