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

send-error

v1.0.1

Published

Send errors as HTTP bodies, with some opinionated, but sensible defaults and conventions

Downloads

8

Readme

send-error

Build Status

Send errors as HTTP bodies, with some opinionated, but sensible defaults and conventions.

Why?

Because errors are important, and I found that having a convention around them helps with making sure that they end up being handled and reported.

How?

var http = require('http')
var sendError = require('send-error')()
var db = require('./db.js')()

function NotFoundError(msg) {
  this.statusCode = 404
  Error.call(this, msg || 'Not found')
}

http.createServer(function(req, res) {
  db.get('foo', function(err, entity) {
    if (err) return sendError(req, res, err)
    if (!entity) return sendError(req, res, new NotFoundError())
    res.writeHead(200, {'content-type': 'application/json'})
    res.end(JSON.stringify(entity))
  })
})

API

SendError(options)

  • options - optional
    • options.contentType (String, optional, defaults to 'application/json') - what Content-Type header to use for errors. This might be useful if your service defines its own Content-Type .
    • options.exclude (Array, optional, defaults to [])- which error properties to exlude from the stringified error.
    • options.includeStack (Boolean)- whether to include stack trace. As including the stack trace in the error is a potential security risk (also, users of your API rarely care about it and you should be reporting it somewhere yourself), this option defaults to false.
    • onerror (Function(http.IncomingMessage, http.ServerResponse, Error), optional) - a function to call when the function returned by the constructor is called. When called, it's passed the request, response and error.

sendError(req, res, error)

Returned by the SendError constructor.

  • req (http.IncomingMessage)
  • req (http.ServerResponse)\
  • err (Error) - error you want to be sent