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-objects

v1.2.0

Published

utilities for returning errors

Downloads

1

Readme

HTTP-friendly error objects

hapijs/boom for browsers. Supports all modern browsers, tested on IE 9+, Chrome 16+, FireFox 5+, Safari 6+, Opera 12+.

Build Status Current Version

error-objects

error-objects provides a set of utilities for returning errors. Each utility returns error response object (instance of Error) which includes the following properties:

  • isBoom - if true, indicates this is a errorObjects instance.
  • isServer - convenience bool indicating status code >= 500.
  • message - the error message.
  • output - the formatted response. Can be directly manipulated after object construction to return a custom error response. Allowed root keys:
    • statusCode - the HTTP status code (typically 4xx or 5xx).
    • headers - an object containing any HTTP headers where each key is a header name and value is the header content.
    • payload - the formatted object used as the response payload (stringified). Can be directly manipulated but any changes will be lost if reformat() is called. Any content allowed and by default includes the following content:
      • statusCode - the HTTP status code, derived from error.output.statusCode.
      • error - the HTTP status message (e.g. 'Bad Request', 'Internal Server Error') derived from statusCode.
      • message - the error message derived from error.message.
  • reformat() - rebuilds error.output using the other object properties.
  • inherited Error properties.

wrap(error, [statusCode], [message])

Decorates an error with the errorObjects properties where:

  • error - the error object to wrap. If error is already a errorObjects object, returns back the same object.
  • statusCode - optional HTTP status code. Defaults to 500.
  • message - optional message string. If the error already has a message, it adds the message as a prefix. Defaults to no message.
var error = new Error('Unexpected input');
errorObjects.wrap(error, 400);

create(statusCode, [message], [data])

Generates an Error object with the errorObjects decorations where:

  • statusCode - an HTTP error code number. Must be greater or equal 400.
  • message - optional message string.
  • data - additional error data set to error.data property.
var error = errorObjects.create(400, 'Bad request', { timestamp: Date.now() });

Thanks

Thanks to Eran Hammer and @hapijs community for the quality engineering behind hapi.