errors icon indicating copy to clipboard operation
errors copied to clipboard

HttpErrors and RestErrors extracted from restify

Results 8 errors issues
Sort by recently updated
recently updated
newest added

restCode must be a string as it defaults to the name of your error constructor

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project. #### Changes included in this PR - Changes to the following...

When sending error with next(error) callback, response sent to client does not contain optionnal properties of my new Error Object created with makeConstructor restify-errors module. Env : Node v12.18.3 with...

I want to set extra options in error response. Didn't find the exact solution anywhere. tried passing in the body ``` const errors = require('restify-errors'); new errors.MethodNotAllowedError({ body: { extra:...

I changed the default error output in restify 4.x using the below code `var restify = require('restify'); var util = require('util'); function ValidationError(message, errors) { restify.RestError.call(this, { restCode: 'ValidationError', statusCode:...

when creating new restify error with a "%25" as a prefix and than one of the following chars (e,E,f,g,G,d etc...) the application will break with an uncaught exception. it looks...

Should be able to just pass an `Error` object and automatically fetch the error message from the `Error` object. For example: ``` javascript return next(new errors.BadRequestError(error)); ``` Instead of _(currently)_:...

fixed but not yet released

File PRs to both [verror](https://github.com/davepacheco/node-verror/) and [bunyan](https://github.com/trentm/node-bunyan) for supporting an error.context property and serializing it. See #21 for more details.