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-handler-json

v2.1.0

Published

Express error handlers for JSON APIs

Downloads

1,384

Readme

error-handler-json

NPM version Build status

An error handler for JSON APIs, meant to be used with http-errors-style errors. The default express error handler returns HTML, but one might want to instead return JSON when designing a pure API instead of a website.

Note: This is a fork of the unmaintained and archived api-error-handler.

Example

const createError = require('http-errors');
const errorHandler = require('error-handler-json');

app.get('/api/endpoint', (req, res) => {
  throw createError(400, 'Invalid data sent');
});

app.use(errorHandler());

A call to /api/endpoint will return a 400 with the following JSON response:

{
  "status": 400,
  "message": "Invalid data sent",
  "name": "BadRequestError",
  "stack": "BadRequestError: ...", // but not in production
}

API

.use(errorHandler([options]))

Options

  • onInternalServerError - Called when handling an status >= 500 error. Default: console.error
  • includeStack - Whether to include err.stack as a property in the returned JSON. Default: !production

Errors

4xx errors are exposed to the client. Properties exposed are:

  • message
  • status
  • name
  • code
  • type
  • stack (optional, see includeStack)
  • any other own properties of the Error object, except for http-errors internals: expose, statusCode

5xx errors that don't have expose set to true are not exposed to the client. Instead, they are given a generic message as well as the status.