chained-error
Advanced tools
Zero dependencies error that allows creating a chain of errors, preserving the original cause (with TypeScript support)
Zero dependencies error that allows creating a chain of errors, preserving the original cause (with TypeScript support)
Install with npm:
$ npm install --save chained-error
import ChainedError from 'chained-error';
// ...
try {
// ...
} catch (error) {
throw new ChainedError('My message', error);
}
Later, when you catch the error, and you print it, you will see something like it:
ChainedError: My message
at ...
at ...
at ...
Caused By: TheOtherErrorType: The other error message
at ...
at ...
at ...
export default class ChainedError extends Error {
cause: any;
constructor(messageOrCause: any);
constructor(message: string, cause: any);
}
MIT
FAQs
Zero dependencies error that allows creating a chain of errors, preserving the original cause (with TypeScript support)
We found that chained-error demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.