Error handler for CLI applications.
Please reach out if you're looking for a Node.js API or CLI engineer (11 years of experience). Most recently I have been Netlify Build's and Netlify Plugins' technical lead for 2.5 years. I am available for full-time remote positions.
- 🖍️ Pretty colors, icons and header
- 💣 Error class-specific handling
- 🚒 Graceful exit
- ⛑️ Normalize invalid errors
- 🔕 Log verbosity: message, stack, properties
- 🚨 Custom exit code
- 💥 Exception-safe
#!/usr/bin/env node
import handleCliError from 'handle-cli-error'
const cliMain = () => {
try {
// ...
} catch (error) {
handleCliError(error) // Logs `error` then exit the process
}
}
cliMain()
handleCliError(error, {
classes: {
InputError: { exitCode: 1, stack: false },
DatabaseError: { exitCode: 2, stack: false },
default: { exitCode: 3 },
},
})
npm install handle-cli-error
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.
error
any
options
Options?
Return value: undefined
Logs error
on the console (stderr
) then exits the process.
This never throws. Invalid errors are silently normalized.
Type: integer
Default: 1
Process exit code.
Note: when passing invalid options
, the exit code is always 125
.
Type: boolean
Default: true
Whether to log the error's stack trace.
Type: boolean
Default: true
Whether to log the error's additional properties.
Type: boolean
Default: false
Exits the process without logging anything on the console.
Type: boolean
Default: true
in terminals, false
otherwise
Whether to colorize the error's message, stack trace and additional properties.
Quoted strings in the error's message are printed in bold (for "..."
and
'...'
) and in italic (for `...`
).
Type: string
Default: 'cross'
Icon prepended to the error's name. The available values are listed here. Can be disabled by passing an empty string.
Type: string
Default: 'red bold'
Color/style of the error's icon and name. The available values are listed here. Several styles can be specified by using spaces. Can be disabled by passing an empty string.
Type: integer
(in milliseconds)
Default: 5000
(5 seconds)
The process exits gracefully: it waits for any ongoing tasks (callbacks,
promises, etc.) to complete, up to a specific timeout
.
Special values:
0
: Exits right away, without waiting for ongoing tasksNumber.POSITIVE_INFINITY
: Waits for ongoing tasks forever, without timing out
Type: object
Default: {}
Specify different options per error class. The object:
- Keys are either the
error.name
, or"default"
(used if noerror.name
matches) - Values are options objects
modern-errors
: Handle errors in a simple, stable, consistent waymodern-errors-cli
: Handle errors in CLI moduleserror-custom-class
: Create one error classerror-class-utils
: Utilities to properly create error classeserror-serializer
: Convert errors to/from plain objectsnormalize-exception
: Normalize exceptions/errorsis-error-instance
: Check if a value is anError
instancemerge-error-cause
: Merge an error with itscause
set-error-class
: Properly update an error's classset-error-message
: Properly update an error's messagewrap-error-message
: Properly wrap an error's messageset-error-props
: Properly update an error's propertiesset-error-stack
: Properly update an error's stackerror-cause-polyfill
: Polyfillerror.cause
log-process-errors
: Show some ❤ to Node.js process errorserror-http-response
: Create HTTP error responseswinston-error-format
: Log errors with Winston
The logo background was created by dgim-studio.
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.
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!