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 #43 I raised the option of using winston to catch unhandled exceptions, however there are more things to consider like process exit events in order to gain proper control of the production system and perform a graceful shutdown. I've been using an npm package called death that we could use as infrastructure, and then use the module lifecycle hook to allow implementations to define shutdown code.
The text was updated successfully, but these errors were encountered:
This would actually be a good way to help shield from sloppy implementation of a process.on('uncaughtException'), as we could call the app's shutdown hook then process.exit along with a log entry
In #43 I raised the option of using winston to catch unhandled exceptions, however there are more things to consider like process exit events in order to gain proper control of the production system and perform a graceful shutdown. I've been using an npm package called death that we could use as infrastructure, and then use the module lifecycle hook to allow implementations to define shutdown code.
The text was updated successfully, but these errors were encountered: