📰 Medium article.

Show some ❤️ to Node.js process errors.

This improves process errors:
uncaught
exceptions,
unhandled
promises, promises
handled too late
and warnings.

Features

- Stack traces for warnings and
rejectionHandled
- Single event handler for all process errors
- Ignore duplicate process errors
- Normalize invalid errors
- Process exit is graceful and can be prevented

Install

Production code (e.g. a server) can install this either as a production or
development dependency:

``bash
npm install log-process-errors
`

However, libraries should install this as a development dependency:

`bash
npm install -D log-process-errors
`

This is because logging is modified globally and libraries users might not
expect this side-effect. Also, this might lead to conflicts between libraries.

This package works in Node.js >=18.18.0.

This is an ES module. It must be loaded using
an import or import() statement,
not require(). If TypeScript is used, it must be configured to
output ES modules,
not CommonJS.

API

logProcessErrors(options?)

options object?\
_Return value_: () => void

Start handling process errors.

`js
import logProcessErrors from 'log-process-errors'
logProcessErrors(options)
`

The return value restores Node.js default behavior.

`js
const restore = logProcessErrors(options)
restore()
`

Options

$3

_Type_: boolean

Whether to exit the process on
uncaught exceptions
or
unhandled promises.

This is false by default if other libraries are listening to those events, so
they can perform the exit instead. Otherwise, this is true.

If some tasks are still ongoing, the exit waits for them to complete up to 3
seconds.

$3

_Type_: (error, event) => Promise | void\
_Default_: console.error(error)

Function called once per process error. Duplicate process errors are ignored.

`js
// Log process errors with Winston instead
logProcessErrors({
onError: (error, event) => {
winstonLogger.error(error.stack)
},
})
`

#### error

_Type_: Error

The process error. This is guaranteed to be a
normalized error instance. A
short description of the event is also appended to its message.

#### event

_Type_: Event

Process event name among:
'uncaughtException',
'unhandledRejection',
'rejectionHandled',
'warning'.

Related projects

- modern-errors: Handle errors in
a simple, stable, consistent way
- modern-errors-process:
Handle process errors
- error-custom-class: Create
one error class
- error-class-utils: Utilities
to properly create error classes
- error-serializer: Convert
errors to/from plain objects
- normalize-exception:
Normalize exceptions/errors
- is-error-instance: Check if
a value is an Error instance
- merge-error-cause: Merge an
error with its cause
- set-error-class: Properly
update an error's class
- set-error-message: Properly
update an error's message
- wrap-error-message:
Properly wrap an error's message
- set-error-props: Properly
update an error's properties
- set-error-stack: Properly
update an error's stack
- error-cause-polyfill:
Polyfill error.cause
- handle-cli-error: 💣 Error
handler for CLI applications 💥
- error-http-response:
Create HTTP error responses
- winston-error-format: Log
errors with Winston

Support

For any question, _don't hesitate_ to submit an issue on GitHub.

Everyone is welcome regardless of personal background. We enforce a
Code of conduct in order to promote a positive and
inclusive environment.

Contributing

This project was made with ❤️. The simplest way to give back is by starring and
sharing it online.

If the documentation is unclear or has a typo, please click on the page's Edit`
button (pencil icon) and suggest a correction.

If you would like to help us fix a bug or add a new feature, please check our
guidelines. Pull requests are welcome!

Thanks go to our wonderful contributors:

ehmicky 💻 🎨 🤔 📖

Steven Vachon 💬

Hongarc 📖 💻

Andy Brenneke 🐛