Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ehmicky/merge-error-cause
Merge an error with its `cause`
https://github.com/ehmicky/merge-error-cause
browser cause code-quality error error-classes error-handler error-handling error-monitoring error-reporting errors exceptions javascript library merge message monitoring nodejs properties stacktrace typescript
Last synced: 3 months ago
JSON representation
Merge an error with its `cause`
- Host: GitHub
- URL: https://github.com/ehmicky/merge-error-cause
- Owner: ehmicky
- License: mit
- Created: 2022-06-09T17:56:45.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2024-09-14T16:52:55.000Z (4 months ago)
- Last Synced: 2024-10-13T00:32:35.354Z (3 months ago)
- Topics: browser, cause, code-quality, error, error-classes, error-handler, error-handling, error-monitoring, error-reporting, errors, exceptions, javascript, library, merge, message, monitoring, nodejs, properties, stacktrace, typescript
- Language: JavaScript
- Homepage:
- Size: 7.66 MB
- Stars: 10
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
[](https://www.npmjs.com/package/merge-error-cause)
[](https://unpkg.com/merge-error-cause?module)
[](/src/main.d.ts)
[](https://codecov.io/gh/ehmicky/merge-error-cause)
[](https://bundlephobia.com/package/merge-error-cause)
[](https://fosstodon.org/@ehmicky)
[](https://medium.com/@ehmicky)
Merge an error with its `cause`.
This merges
[`error.cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause)
recursively with its parent `error`, including its
[`message`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/message),
[`stack`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/stack),
[`name`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/name)
and
[`errors`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/AggregateError).
# Hire me
Please
[reach out](https://www.linkedin.com/feed/update/urn:li:activity:7117265228068716545/)
if you're looking for a Node.js API or CLI engineer (11 years of experience).
Most recently I have been [Netlify Build](https://github.com/netlify/build)'s
and [Netlify Plugins](https://www.netlify.com/products/build/plugins/)'
technical lead for 2.5 years. I am available for full-time remote positions.
# Example
```js
import mergeErrorCause from 'merge-error-cause'
const main = (userId) => {
try {
return createUser(userId)
} catch (error) {
throw mergeErrorCause(error)
// Printed as:
// TypeError: Invalid user id: false
// Could not create user.
}
}
const createUser = (userId) => {
try {
validateUserId(userId)
return sendDatabaseRequest('create', userId)
} catch (cause) {
throw new Error('Could not create user.', { cause })
}
}
const validateUserId = (userId) => {
if (typeof userId !== 'string') {
throw new TypeError(`Invalid user id: ${userId}.`)
}
}
main(false)
```
# Install
```bash
npm install merge-error-cause
```
This package works in both Node.js >=18.18.0 and
[browsers](https://raw.githubusercontent.com/ehmicky/dev-tasks/main/src/browserslist).
This is an ES module. It must be loaded using
[an `import` or `import()` statement](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c),
not `require()`. If TypeScript is used, it must be configured to
[output ES modules](https://www.typescriptlang.org/docs/handbook/esm-node.html),
not CommonJS.
# API
## mergeErrorCause(error)
`error` `Error | any`\
_Return value_: `Error`
`error` is modified and returned.
If `error`'s class is `Error` or if [`error.wrap`](#error-class) is `true`,
[`error.cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause)
is modified and returned instead.
If `error` is not a valid `Error`, a new `error` is created and returned
instead.
This never throws.
# Background
[`error.cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause)
is a
[recent](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error/cause#browser_compatibility)
JavaScript feature to wrap error messages and properties.
```js
try {
validateUserId(userId)
sendDatabaseRequest('create', userId)
} catch (cause) {
throw new Error('Could not create user.', { cause })
}
```
However, it comes with a few issues.
## Traversing `error.cause`
### Problem
Consumers need to traverse `error.cause`.
```js
try {
createUser(userId)
} catch (error) {
if (error.code === 'E101' || (error.cause && error.cause.code === 'E101')) {
// Checking for properties requires traversing `error.cause`
}
if (
error.name === 'UserError' ||
(error.cause && error.cause.name === 'UserError')
) {
// So does checking for error class
}
}
```
This is tricky to get right. For example:
- `error.cause.cause` might also exist (and so on)
- If `error` is not an `Error` instance, `error.name` might throw
- Recursing over `error.cause` might be an infinite cycle
### Solution
This library merges `error.cause` recursively. It also
[ensures `error` is an `Error` instance](#normalization). Consumers can then
handle errors without checking its `cause`.
```js
try {
createUser(userId)
} catch (error) {
if (error.code === 'E101') {
/* ... */
}
if (error.name === 'UserError') {
/* ... */
}
}
```
## Verbose stack trace
### Problem
Stack traces with multiple `error.cause` can be quite verbose.
```
Error: Could not create user group.
at createUserGroup (/home/user/app/user_group.js:19:9)
at createGroups (/home/user/app/user_group.js:101:10)
at startApp (/home/user/app/app.js:35:20)
at main (/home/user/app/app.js:3:4) {
[cause]: Error: Could not create user.
at newUser (/home/user/app/user.js:52:7)
at createUser (/home/user/app/user.js:43:5)
at createUserGroup (/home/user/app/user_group.js:17:11)
at createGroups (/home/user/app/user_group.js:101:10)
at startApp (/home/user/app/app.js:35:20)
at main (/home/user/app/app.js:3:4) {
[cause]: Error: Invalid user.
at validateUser (/home/user/app/user.js:159:8)
at userInstance (/home/user/app/user.js:20:4)
at newUser (/home/user/app/user.js:50:7)
at createUser (/home/user/app/user.js:43:5)
at createUserGroup (/home/user/app/user_group.js:17:11)
at createGroups (/home/user/app/user_group.js:101:10)
at startApp (/home/user/app/app.js:35:20)
at main (/home/user/app/app.js:3:4) {
[cause]: UserError: User "15" does not exist.
at checkUserId (/home/user/app/user.js:195:3)
at checkUserExist (/home/user/app/user.js:170:10)
at validateUser (/home/user/app/user.js:157:23)
at userInstance (/home/user/app/user.js:20:4)
at newUser (/home/user/app/user.js:50:7)
at createUser (/home/user/app/user.js:43:5)
at createUserGroup (/home/user/app/user_group.js:17:11)
at createGroups (/home/user/app/user_group.js:101:10)
at startApp (/home/user/app/app.js:35:20)
at main (/home/user/app/app.js:3:4)
}
}
}
```
Each error cause is indented and printed separately.
- The stack traces mostly repeat each other since the function calls are part of
the same line execution
- The most relevant message (innermost) is harder to find since it is shown last
### Solution
This library only keeps the innermost stack trace. Error messages are
concatenated by default from innermost to outermost. This results in much
simpler stack traces without losing any information.
```
TypeError: User "15" does not exist.
Invalid user.
Could not create user.
Could not create user group.
at checkUserId (/home/user/app/user.js:195:3)
at checkUserExist (/home/user/app/user.js:170:10)
at validateUser (/home/user/app/user.js:157:23)
at userInstance (/home/user/app/user.js:20:4)
at newUser (/home/user/app/user.js:50:7)
at createUser (/home/user/app/user.js:43:5)
at createUserGroup (/home/user/app/user_group.js:17:11)
at createGroups (/home/user/app/user_group.js:101:10)
at startApp (/home/user/app/app.js:35:20)
at main (/home/user/app/app.js:3:4)
```
# Features
## Stack traces
Only the innermost stack trace is kept.
Please make sure you use `async`/`await` instead of `new Promise()` or callbacks
to prevent truncated stack traces.
## Messages
Inner error messages are printed first.
```js
try {
throw new Error('Invalid user id.')
} catch (cause) {
throw new Error('Could not create user.', { cause })
// Printed as:
// Error: Invalid user id.
// Could not create user.
}
```
If the outer error message ends with `:`, it is prepended instead.
```js
try {
throw new Error('Invalid user id.')
} catch (cause) {
throw new Error('Could not create user:', { cause })
// Printed as:
// Error: Could not create user: Invalid user id.
}
```
`:` can optionally be followed by a newline.
```js
try {
throw new Error('Invalid user id.')
} catch (cause) {
throw new Error('Could not create user:\n', { cause })
// Printed as:
// Error: Could not create user:
// Invalid user id.
}
```
## Error class
The outer error class is used.
```js
try {
throw new TypeError('User id is not a string.')
} catch (cause) {
const error = new UserError('Could not create user.', { cause })
const mergedError = mergeErrorCause(error)
console.log(mergedError instanceof UserError) // true
console.log(mergedError.name) // 'UserError'
}
```
If the parent error class is `Error`, the child class is used instead. This
allows wrapping the error message or properties while keeping its class.
```js
try {
throw new TypeError('User id is not a string.')
} catch (cause) {
const error = new Error('Could not create user.', { cause })
console.log(mergeErrorCause(error) instanceof TypeError) // true
}
```
`error.wrap: true` has the same effect, but works with any parent error class.
```js
try {
throw new TypeError('User id is not a string.')
} catch (cause) {
const error = new UserError('Could not create user.', { cause })
error.wrap = true
console.log(mergeErrorCause(error) instanceof TypeError) // true
}
```
## Error properties
Error properties are shallowly merged.
```js
// Both `userId` and `invalidUser` are kept
try {
throw Object.assign(new Error('Invalid user id.'), { userId: '5' })
} catch (cause) {
throw Object.assign(new Error('Could not create user.', { cause }), {
invalidUser: true,
})
}
```
Empty error messages are ignored. This is useful when wrapping error properties.
```js
try {
throw new Error('Invalid user id.')
} catch (cause) {
throw Object.assign(new Error('', { cause }), { invalidUser: true })
}
```
## Aggregate errors
Any
[`aggregateError.errors[*].cause`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/AggregateError)
is processed recursively. However, `aggregateError.errors` are not merged with
each other since those are different from each other.
If both `error.errors` and `error.cause.errors` exist, they are concatenated.
## Normalization
Invalid errors [are normalized](https://github.com/ehmicky/normalize-exception)
to proper `Error` instances.
```js
try {
throw 'Invalid user id.'
} catch (error) {
console.log(mergeErrorCause(error)) // Error: Invalid user id.
}
```
# Related projects
- [`modern-errors`](https://github.com/ehmicky/modern-errors): Handle errors in
a simple, stable, consistent way
- [`error-custom-class`](https://github.com/ehmicky/error-custom-class): Create
one error class
- [`error-class-utils`](https://github.com/ehmicky/error-class-utils): Utilities
to properly create error classes
- [`error-serializer`](https://github.com/ehmicky/error-serializer): Convert
errors to/from plain objects
- [`normalize-exception`](https://github.com/ehmicky/normalize-exception):
Normalize exceptions/errors
- [`is-error-instance`](https://github.com/ehmicky/is-error-instance): Check if
a value is an `Error` instance
- [`set-error-class`](https://github.com/ehmicky/set-error-class): Properly
update an error's class
- [`set-error-message`](https://github.com/ehmicky/set-error-message): Properly
update an error's message
- [`wrap-error-message`](https://github.com/ehmicky/wrap-error-message):
Properly wrap an error's message
- [`set-error-props`](https://github.com/ehmicky/set-error-props): Properly
update an error's properties
- [`set-error-stack`](https://github.com/ehmicky/set-error-stack): Properly
update an error's stack
- [`error-cause-polyfill`](https://github.com/ehmicky/error-cause-polyfill):
Polyfill `error.cause`
- [`handle-cli-error`](https://github.com/ehmicky/handle-cli-error): 💣 Error
handler for CLI applications 💥
- [`log-process-errors`](https://github.com/ehmicky/log-process-errors): Show
some ❤ to Node.js process errors
- [`error-http-response`](https://github.com/ehmicky/error-http-response):
Create HTTP error responses
- [`winston-error-format`](https://github.com/ehmicky/winston-error-format): Log
errors with Winston
# Support
For any question, _don't hesitate_ to [submit an issue on GitHub](../../issues).
Everyone is welcome regardless of personal background. We enforce a
[Code of conduct](CODE_OF_CONDUCT.md) 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](CONTRIBUTING.md). Pull requests are welcome!