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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@raggedkarma/errors

v1.0.1

Published

An error set for easy HTTP error responses

Readme

An error set for easy HTTP error responses.

This is an extension of super-error. Every error defined in this package behaves as presented in that package.

Use the following errors to wrap additional HTTP response information to an error:

  • BadRequestError for HTTP 400 Bad Request
  • UnauthorizedError for HTTP 401 Unauthorized
  • ForbiddenError for HTTP 403 Forbidden
  • NotFoundError for HTTP 404 Not Found
  • TooManyRequestsError for HTTP 429 Too Many Requests
  • InternalServerError for HTTP 500 Internal Server Error

All of these errors accept two arguments: message, and details. Error details are expected to be an array of objects, each detailing an error. This is to allow for bulk response, such as in the case of validation errors.

Example

const errors = require("@raggedkarma/errors");

...
.catch(e => {
    var err new errors.BadRequestError("Validation Errors", [{"message": "Name is required", "field": "name"}, ...]).causedBy(e);
});
...

// Express
res.status(err.code);
if (!err.message) return res.send();
res.json({
    "errors": err.details
});

The package also presents a knows static function, so you can quickly verify if an error response has been previously wrapped by an error defined by this package.

Testing

Use npm install && npm test to run all tests, and npm coverage to generate a full coverage report.