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

error-page

v0.0.7

Published

Easily send errors in Node.js HTTP servers. Think like the `ErrorDocument` declarations in Apache config files.

Downloads

75

Readme

error-page

Easily send errors in Node.js HTTP servers.

Think like the ErrorDocument declarations in Apache config files.

Usage

var ErrorPage = require('error-page')

http.createServer(function (req, res) {
  // returns a function that we use to send error responses
  res.error = ErrorPage(req, res, { // options
    404: the404HandlerFunction,
    5xx: handleAll500s,
    403: 'forbidden.ejs', // template name integrates with Templar
    400: 'that was bad', // other strings just print out as-is
    "*": handleEverythingElse
    debug: false // show full stack traces, or just messages
  })

  // .. some time later ..
  // .. we've decided that the page doesn't exist ..
  return res.error(404)

  // or maybe we decided that the request method is no good...
  // Give a little extra bit on the message.
  return res.error(405, "Allowed methods: GET, POST, HEAD")

  // or maybe they just need to try again in 10 seconds
  return res.error(503, {'retry-after':10})

  // or maybe we are a teapot
  return res.error(418)

  // or maybe something threw
  try {
    blerg()
  } catch (er) {
    return res.error(er)
  }
})

Any arguments to the res.error function will be interpreted based on their type:

  • Number: the status code (defaults to 500, if it can't find one)
  • Error object: Some error that was thrown or raised somewhere (with a stack, etc.)
  • Other object: Bag o' headers which get set on the response.
  • Function: A handler to use, instead of the one set up initially
  • String: If there's a res.template from Templar, and it's a valid template name, then it'll use the template as the handler.
  • String that is not a template: A message (defaults to the message property on the Error object, if one was supplied, or the default message associated with the status code.)

The handler (or template) is called with the request and response objects, and a data object containing:

data = { message: message
       , code: code
       , statusCode: code
       , error: er
       , options: opts
       , request: req.method + ' ' + req.url
       , headers: req.headers
       , url: req.url
       }