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

easy-http-errors

v2.0.0

Published

Easy HTTP errors

Downloads

4,674

Readme

Easy Http Errors

npm node Build Status Coverage Status

A preset of HTTP errors that can be easily used to throw errors in your applications.

Installation

NPM

npm i easy-http-errors --save

Yarn

yarn add easy-http-errors

Usage

// ES6 import.
import { BadRequestError } from 'easy-http-errors';

// Throw the default bad request.
throw new BadRequestError();

// Throw a bad request with a custom message and properties.
throw new BadRequestError('Ups, this is a bad request', { foo: 'bar' });

List of errors

| Status Code | Name | | :---------: | -----------------------------------| | 400 | BadRequestError | | 401 | UnauthorizedError | | 402 | PaymentRequiredError | | 403 | ForbiddenError | | 404 | NotFoundError | | 405 | MethodNotAllowedError | | 406 | NotAcceptableError | | 407 | ProxyAuthenticationRequiredError | | 408 | RequestTimeoutError | | 409 | ConflictError | | 410 | GoneError | | 411 | LengthRequiredError | | 412 | PreconditionFailedError | | 413 | PayloadTooLargeError | | 414 | URITooLongError | | 415 | UnsupportedMediaTypeError | | 416 | RangeNotSatisfiableError | | 417 | ExpectationFailedError | | 418 | ImATeapotError | | 421 | MisdirectedRequestError | | 422 | UnprocessableEntityError | | 423 | LockedError | | 424 | FailedDependencyError | | 425 | UnorderedCollectionError | | 426 | UpgradeRequiredError | | 428 | PreconditionRequiredError | | 429 | TooManyRequestsError | | 431 | RequestHeaderFieldsTooLargeError | | 451 | UnavailableForLegalReasonsError | | 500 | InternalServerError | | 501 | NotImplementedError | | 502 | BadGatewayError | | 503 | ServiceUnavailableError | | 504 | GatewayTimeoutError | | 505 | HTTPVersionNotSupportedError | | 506 | VariantAlsoNegotiatesError | | 507 | InsufficientStorageError | | 508 | LoopDetectedError | | 509 | BandwidthLimitExceededError | | 510 | NotExtendedError | | 511 | NetworkAuthenticationRequiredError |

Tests

Run the tests from the root directory:

npm test

Contributing & Development

Contributing

Found a bug or want to suggest something? Take a look first on the current and closed issues. If it is something new, please submit an issue.

Develop

It will be awesome if you can help us evolve easy-http-errors. Want to help?

  1. Fork it.
  2. npm install.
  3. Hack away.
  4. Run the tests: npm test.
  5. Create a Pull Request.