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

serialize-http-error

v1.1.0

Published

Prepare an Error for JSON serialization

Downloads

192

Readme

Serialize HTTP Error

NPM Version Build Status Code Coverage

Serializes any input (preferrably an Error) to a plain old JavaScript Object which has the following guarantees:

  1. The error will be exposed if:

    • The NODE_ENV is "development", or;
    • The expose option is true, or;
    • the expose property is true, or;
    • the status property contains a number less than 500.
  2. Has at least a name property and a message property, both always Strings. They default to "Error" and "Something went wrong"

  3. Other enumerable properties are copied under the following conditions:

    • The error is exposed, and;
    • the property is safe for JSON.stringify (unless unsafe).

Usage

const serializeHttpError = require('serialize-http-error');
const app = require('express')();

app.use((err, req, res, next) => {
  res.status(err.status || 500);
  res.json(serializeHttpError(err));
});

Options

The second argument to serializeHttpError may be an object with options, eg:

serializeHttpError(err, {
  unsafe: true,
  flat: true,
  expose: false
});

unsafe

false

If set to true, all enumerable properties, even recursive ones, will be copied. This allows for customized resolution of these properties, for example by using the replacer argument in JSON.stringify.

flat

false

By default, nested Error objects are also serialized. If set to true, they will be left intact.

expose

process.env.NODE_ENV === 'development'

If set to true, all errors will be exposed. If set to false, only exposable errors are exposed.

defaultName

'Error'

The default name to use for values which don't have a name, or errors which may not be exposed.

defaultMessage

'Something went wrong'

The default message to use for values which don't have a message, or errors which may not be exposed.