log-process-errors

Log any process errors:

• uncaughtException: an exception was thrown and not caught
• unhandledRejection: a promise was rejected and not handled
• rejectionHandled: a promise was rejected and handled too late
• multipleResolves: a promise was resolved/rejected twice
• warning: a warning was produced using process.emitWarning()

Usage

const logProcessErrors = require('log-process-errors')

const undoSetup = lopProcessErrors.setup()

When any process errors occur, it will be logged using console.error(). The message will include detailed information about the error.

For warning, console.warn() will be used instead.

You can undo everything by firing the function returned by onProcessError.setup() (called undoSetup in the example above).

Example output

TO BE DONE

Custom handling

You can override the default behavior by passing a custom function to the handle option.

onProcessError.setup({
  handle({ eventName, promiseState, promiseValue, error, message }) {},
})

This can be useful if you want to use your own logger instead of the console.

The function's argument is an object with the following properties:

• eventName {string}: can be uncaughtException, unhandledRejection, rejectionHandled, multipleResolves or warning
• error {any} is either:
  • value thrown by uncaughtException. Usually an Error instance, but not always.
  • Error instance emitted by warning. error.name, error.code and error.detail might be defined.
• promiseState {string}: whether promise was resolved or rejected. For unhandledRejection, rejectionHandled and multipleResolves.
• promiseValue {any}: value resolved/rejected by the promise. For unhandledRejection, rejectionHandled and multipleResolves.
• message {string}: detailed message summing up all of the above.

Exiting on uncaught exceptions

By default, uncaughtException will fire process.exit(1). This is the recommended behavior according to the Node.js documentation.

You can disable this by setting the exitOnExceptions option to false:

onProcessError.setup({ exitOnExceptions: false })