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

node-http-error

v2.0.0

Published

Error subclasses for returning HTTP errors

Downloads

1,918

Readme

Pretty HTTP Errors for Node

Ever wanted to build an API with Node and constantly had to either use blocks to return errors so you could attach a status code, or you just use one type of status code for all errors? Now you can throw your errors in just one line.

npm install node-http-error

Build Status

Example

var HTTPError = require('node-http-error');
var app = require('express')();

app.get('/error', function(req, req, next) {
  return next(new HTTPError(500, 'Error by design.'));
});

// Error handler
app.use(function(err, req, res, next) {
  res.status(err.status); // or use err.statusCode instead
  res.send(err.message);
});

app.listen(2000);
$ curl -i http://localhost:2000/error

HTTP/1.1 500 Internal Server Error
X-Powered-By: Express
Content-Type: application/json; charset=utf-8
Content-Length: 51
ETag: W/"33-2476597395"
Date: Thu, 14 Aug 2014 17:51:07 GMT
Connection: keep-alive

Error by design.

Features

  • Treat it just like Error. HTTPError's are throwable, have full stacktrace, and even print out their status code when they're thrown.
  • Don't worry about accidentally forgetting the new operator, HTTPError works without it.
  • Give it just the HTTP status code you want to return, and the error message is automatically generated.
  • Assign extra properties to the error.

Usage

HTTPError(status, message, properties)

Creates an error with the given status, message and properties. For example

   new HTTPError(404, 'Not found!', { path: '/something-missing' })

HTTPError(status, message)

Creates an error message with the given status and message.

HTTPError(message)

Creates an error message with the message and 500 as the status code (Internal Server Error).

HTTPError(status)

Creates an error message with the given status. The error message is looked up from the default Node HTTP module. For example, HTTPError(404) is equivalent to HTTPError(404, 'Not Found').

The Node HTTP module is not loaded unless needed to lookup the error message.