allhttperrors
Advanced tools
A module to create flexible, powerful Error objects based on HTTP responses
This is a simple module to create HTTP error constructor based on Node's http.STATUS_CODES information.
How to use it:
var errors = require( 'allhttperrors' );
var e = new errors.UnauthorizedError();
console.log( e.httpError ); // 401
// ...
next( new errors.NotFoundError() );
// ... or:
next( new errors.NotFoundError("The file specified could not be found") );
// ... or:
next( new errors.NotFoundError(
{ message: "The file specified could not be found", extraInfo: { fileName: 'someFile' } }
) );
The error names are based on the default messages set by nodejs, with strange characters stripped out and capitalisation added. See the bottom of this file for the full list of errors constructors created.
By default, each error constructor sets:
this.message; if no parameter is passed, it's the name of the error. If a string is passed, then this.message will be assigned to it; if an object is passed, then this.message will be assigned passedObject.message.
this.httpError; automatically set depending on the HTTP error
By looking at the code above, you probably noticed that the last form of constucting an error shows that the constructor's parameters are very flexible. The constructor can be called in three forms:
NotFoundError(). This will create an error of type NotFoundError, where this.message is Not found.NotFoundError( 'Custom message' ). This will create an error of type NotFoundError, where this.message is Custom Message.NotFoundError( { message: "Custom message", filename: 'log.txt' } ). This will create an error of type NotFoundError, where this.message is Custom Message and this.fileName is log.txt. Basically, the passed object will be mixed into the created object.If you pass an passedObject to the constructor as a parameter, then every attribute of passedObject will be mixed into the object itself. This is really handy if you want to attach extra information to your error objects. If you are using express, your error handler might look into the err variable and use the extra information.
Note: Only the first parameter is standard in the creation of the Error object. In Firefox, it is new Error([message[, fileName[, lineNumber]]]), in IE it is new Error([number[, description]]), in Chrome, new Error(description, constr). I made the constructor as standard as possible: new Error("Message"), the basic use case, works.
Here is a full list of error constructors defined by the module:
ContinueError: ContinueSwitchingProtocolsError: Switching ProtocolsProcessingError: ProcessingOKError: OKCreatedError: CreatedAcceptedError: AcceptedNonAuthoritativeInformationError: Non-Authoritative InformationNoContentError: No ContentResetContentError: Reset ContentPartialContentError: Partial ContentMultiStatusError: Multi-StatusMultipleChoicesError: Multiple ChoicesMovedPermanentlyError: Moved PermanentlyMovedTemporarilyError: Moved TemporarilySeeOtherError: See OtherNotModifiedError: Not ModifiedUseProxyError: Use ProxyTemporaryRedirectError: Temporary RedirectBadRequestError: Bad RequestUnauthorizedError: UnauthorizedPaymentRequiredError: Payment RequiredForbiddenError: ForbiddenNotFoundError: Not FoundMethodNotAllowedError: Method Not AllowedNotAcceptableError: Not AcceptableProxyAuthenticationRequiredError: Proxy Authentication RequiredRequestTimeOutError: Request Time-outConflictError: ConflictGoneError: GoneLengthRequiredError: Length RequiredPreconditionFailedError: Precondition FailedRequestEntityTooLargeError: Request Entity Too LargeRequestURITooLargeError: Request-URI Too LargeUnsupportedMediaTypeError: Unsupported Media TypeRequestedRangeNotSatisfiableError: Requested Range Not SatisfiableExpectationFailedError: Expectation FailedIMATeapotError: I'm a teapotUnprocessableEntityError: Unprocessable EntityLockedError: LockedFailedDependencyError: Failed DependencyUnorderedCollectionError: Unordered CollectionUpgradeRequiredError: Upgrade RequiredPreconditionRequiredError: Precondition RequiredTooManyRequestsError: Too Many RequestsRequestHeaderFieldsTooLargeError: Request Header Fields Too LargeInternalServerErrorError: Internal Server ErrorNotImplementedError: Not ImplementedBadGatewayError: Bad GatewayServiceUnavailableError: Service UnavailableGatewayTimeOutError: Gateway Time-outHTTPVersionNotSupportedError: HTTP Version not supportedVariantAlsoNegotiatesError: Variant Also NegotiatesInsufficientStorageError: Insufficient StorageBandwidthLimitExceededError: Bandwidth Limit ExceededNotExtendedError: Not ExtendedNetworkAuthenticationRequiredError: Network Authentication RequiredFAQs
A module to create flexible, powerful Error objects based on HTTP responses
The npm package allhttperrors receives a total of 6 weekly downloads. As such, allhttperrors popularity was classified as not popular.
We found that allhttperrors 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
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.
Security News
The npm package for the LottieFiles Player web component was hit with a supply chain attack after a software engineer's npmjs credentials were compromised.