Throwing errors in Javascript does not give much information about the error type as it is really hard to throw custom exceptions. Node Exceptions is a tiny wrapper which will let you extend the Error class and throw custom errors.
Errors are thrown anywhere inside the code and handling them properly is required. For example you have an HTTP application, which can throw multiple errors and in order to handle those errors gracefully, you need to know the error types or their names.
switch (err.name) {
case 'HttpException':
// do something
case 'RunTimeException':
// do something else
}
npm i --save node-exceptions
const NE = require('node-exceptions')
class MyCustomError extends NE.LogicalException {}
try {
throw new MyCustomError('Something bad happened')
} catch (e) {
console.log(e.status) // equals 500
console.log(e.name) // equals MyCustomError
console.log(e.message) // Something bad happened
console.log(e.stack) // Error stack with correct reference to filepath and linenum
console.log(e.toString()) // MyCustomError: Something bad happened
}
It is also possible to have a custom error status when throwing exceptions.
const NE = require('node-exceptions')
class HttpException extends NE.LogicalException {}
try {
throw new HttpException('Page not found', 404)
} catch (e) {
console.log(e.status) // equals 404
}
Also NE
comes with some commonly required Exception classes which includes.
When something excepted has failed. For example image upload mismatch extension.
throw new NE.DomainException()
Method arguments are invalid or incomplete.
throw new NE.InvalidArgumentException()
Error caused due to arithmetic operations.
throw new NE.RangeException()
An error occured after all required checks.
throw new NE.RuntimeException()
Http specific errors.
throw new NE.HttpException()
Generated using TypeDoc