npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

generic-errors

v2.3.1

Published

Generic errors with common http codes

Downloads

885

Readme

generic-errors

Generic error constructors with common http codes.

Also doesn't pollute the stack with its own depth.

Usage

Install:

npm install generic-errors

Require the errors:

const errors = require('generic-errors');

Use an error:

const notFound = new errors.NotFound('Could not find the thing');

Add additional Properties to the error

const unprocessable = new errors.Unprocessable({ message: 'Cant Process', fields: ['foo', bar] });

Available constructors:

BaseError                       // 500 Use to make custom errors, easier to inherit from than Error
BadRequest                      // 400
Unauthorised                    // 401
Forbidden                       // 403
NotFound                        // 404
MethodNotAllowed                // 405
NotAcceptable                   // 406
ProxyAuthenticationRequired     // 407
RequestTimeout                  // 408
Conflict                        // 409
Gone                            // 410
LengthRequired                  // 411
PreconditionFailed              // 412
PayloadTooLarge                 // 413
URITooLong                      // 414
UnsupportedMediaType            // 415
RangeNotSatisfiable             // 416
ExpectationFailed               // 417
Teapot                          // 418
Unprocessable                   // 422
TooEarly                        // 425
UpgradeRequired                 // 426
PreconditionRequired            // 428
TooManyRequests                 // 429
RequestHeaderFieldsTooLarge     // 431
UnavailableForLegalReasons      // 451
NotImplemented                  // 501
BadGateway                      // 502
ServiceUnavailable              // 503
GatewayTimeout                  // 504
HTTPVersionNotSupported         // 505
VariantAlsoNegotiates           // 506
NotExtended                     // 510
NetworkAuthenticationRequired   // 511

Detection

After serialization Generic Errors can still be detected using the isGenericError function attacted to the BaseError constructor.

    const notFound = new errors.NotFound();
    const serializedError = JSON.parse(JSON.stringify(notFound));

    errors.BaseError.isGenericError(serializedError);  // true