Security News
Node.js EOL Versions CVE Dubbed the "Worst CVE of the Year" by Security Experts
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
custom-error-generator
Advanced tools
Custom errors and exceptions in Node.js
$ npm install custom-error-generator --save
var createCustomError = require('custom-error-generator');
var ValidationError = createCustomError('ValidationError', { 'required', 'Missing parameter x' }, TypeError);
var HTTPError = createCustomError('HTTPError', { 'code' : 500, 'status' : 'Server Error' });
throw new ValidationError('Required');
The generator function supports the following parameters:
name
{String} (required) - A custom name for this error type, which is printed when logging and in stack traces
data
{Object} (optional) - Additional properties to attach to the error, in key=value pairs or as object descriptors
Constructor
{Function} (optional) - A function to inherit from. Allows for additional methods and properties to be defined on your custom errors
The errors created by the generated functions are identical to built-in Error objects, with additional features such as:
Custom properties can be attached and accessed at run time:
var error = new HTTPError('Uh oh');
console.log(error.code, error.status); // prints 500 Server Error
Similar to console.log
, the custom error message will be formatted from all available string and number arguments, using util.format
:
var error = new ValidationError('%s: %s', 'Missing Field', 'name');
console.log(error); // prints ValidationError: Missing Field: name
Other error objects can be passed in as arguments, which augment the original error stack trace with their own stack traces:
var error = new ValidationError('Missing field');
var serverError = new HTTPError('Something went wrong', error);
console.log(serverError.stack);
outputs:
HTTPError: Something went wrong
at Context.<anonymous> (/Projects/node-custom-error/test.js:19:24)
at callFn (/Projects/node-custom-error/node_modules/mocha/lib/runnable.js:223:21)
at Hook.Runnable.run (/Projects/node-custom-error/node_modules/mocha/lib/runnable.js:216:7)
at next (/Projects/node-custom-error/node_modules/mocha/lib/runner.js:259:10)
at Object._onImmediate (/Projects/node-custom-error/node_modules/mocha/lib/runner.js:276:5)
at processImmediate [as _immediateCallback] (timers.js:330:15)
ValidationError: Missing field
at Context.<anonymous> (/Projects/node-custom-error/test.js:18:24)
at callFn (/Projects/node-custom-error/node_modules/mocha/lib/runnable.js:223:21)
at Hook.Runnable.run (/Projects/node-custom-error/node_modules/mocha/lib/runnable.js:216:7)
at next (/Projects/node-custom-error/node_modules/mocha/lib/runner.js:259:10)
at Object._onImmediate (/Projects/node-custom-error/node_modules/mocha/lib/runner.js:276:5)
at processImmediate [as _immediateCallback] (timers.js:330:15)
Multiple error objects are allowed to be passed, and are processed in order.
Errors can also be serialized into JSON format by using error#toJSON();
. This will enumerate all of the hidden and custom properties, and also format the stack trace into an array of individual lines:
console.log(error.toJSON()); // or console.log(JSON.stringify(error));
outputs
{ stack:
[ 'ValidationError: Missing field',
' at Context.<anonymous> (/Projects/node-custom-error/test.js:17:24)',
' at callFn (/Projects/node-custom-error/node_modules/mocha/lib/runnable.js:223:21)',
' at Hook.Runnable.run (/Projects/node-custom-error/node_modules/mocha/lib/runnable.js:216:7)',
' at next (/Projects/node-custom-error/node_modules/mocha/lib/runner.js:259:10)',
' at Object._onImmediate (/Projects/node-custom-error/node_modules/mocha/lib/runner.js:276:5)',
' at processImmediate [as _immediateCallback] (timers.js:330:15)' ],
arguments: undefined,
type: undefined,
required: 'Missing parameter x',
message: 'Missing Field' }
Finally, a custom function can be passed in as a 3rd argument. This will allow you to modify the custom error prototype without having to modify the original native Error prototype:
var HTTPError = createCustomError('HTTPError', null, function (message, code) {
var http = require('http');
// Set custom properties when thrown based on additional arguments
this.code = code;
this.status = http.STATUS_CODES[code];
// We can override the default message logic if desired:
this.message = message;
});
var error = new HTTPError('You do not have permission', 403);
console.log(error, [error.code, error.status]);
// result: HTTPError: You do not have permission [ 403, "Forbidden" ]
Care is taken to preserve the built-in error handling behavior as much as possible, supporting:
custom instanceOf Error
Error.prototype.isPrototypeOf(custom)
util.isError(custom)
custom = generator('message')
custom = new generator('message');
In other words, you shouldn't have to worry about these errors affecting your syntax or existing code. Simply drop in place for any existing errors you're throwing and it should work just the same.
FAQs
Custom errors and exceptions in Node.js
We found that custom-error-generator 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.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.