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

@financial-times/ip-custom-errors

v1.0.1

Published

Generates custom Http errors

Downloads

111

Readme

ip-custom-errors

npm version CircleCI

A module that generates custom HTTP errors

setup

Install via npm:

  npm i -S @financial-times/ip-custom-errors

Usage

The module exposes three methods to generate the custom HTTP errors. You can use the one that fits your needs as follows:

Using the custom HttpError constructor to create a custom error message, for example:

const { HTTPError } = require('@financial-times/ip-custom-errors');
try {
  ...
  throw new HTTPError(401,'Unauthorized','You are not allowed to access this resource')
} catch (err) {
  console.error(err)
}

Using the custom HTTPStatusError method with status code and custom message, for example:

const { HTTPStatusErrors } = require('@financial-times/ip-custom-errors');
try {
  ...
  throw HTTPStatusErrors['400']('You are not allowed to access this resource')
} catch (err) {
  console.error(err)
}

Using the name of the custom error by name

const { NotFound } = require('@financial-times/ip-custom-errors');
try {
  ...
  throw NotFound("The resource you requested can't be found");
} catch (err) {
  console.error(err)
}

List of error names to use

|||| |:-----------------------------|:--------------------------|:-----------------------------| | BadRequest | UnsupportedMediaType | NotImplemented |
| Unauthorized | RangeNotSatisfiable | BadGateway |
| PaymentRequired | Expectation | HttpVersionNotSupported |
| Forbidden | MisdirectedRequest | VariantAlsoNegotiates |
| NotFound | UnprocessableEntity | InsufficientStorage |
| MethodNotAllowed | Locked | LoopDetected |
| NotAcceptable | UnorderedCollection | NotExtended| | | ProxyAuthenticationRequired | UpgradeRequired | NetworkAuthenticationRequired|
| RequestTimeout | PreconditionRequired | ServiceUnavailable |
| Conflict | TooManyRequests | GatewayTimeout | | Gone | UnavailableForLegalReasons| BandwidthLimitExceeded | | LengthRequired | InternalServerError | | PreconditionFailed | ImATeapot | | PayloadTooLarge | FailedDependency | | UriTooLong | RequestHeaderFieldsTooLarge |

Licence

MIT