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

@aequum/exceptions

v0.27.15

Published

aequum common exceptions collection

Readme

aequum common exceptions collection

This package provides a set of rich, descriptive and detailed exceptions interfaces, classes and types to have an standard way to handle show errors and providing the right information to the user or developer when an error occurs in the application.

Design

Each exception class must have:

  • A text code for error, we use ERR_ prefix and uppercase snake case.
  • An HTTP status code for the error is available but isn't mandatory by default it uses a 500 error code.
  • A human readable message that describes the error.
  • An input object or struct to show the input that caused the error, on some complex cases it have an structured object with more details, as in case of ValidationException.
  • Also one of the base constructor arguments are the cause of the error if it derives from another exception, this is useful to trace the error back to its origin.

Classes

Base:

Authorization:

Data:

Validation:

  • ValidationException: Validation exception, for input objects, this exception have an structured output for input property, representing the input property validated and it's corresponding error messages.

Interfaces

  • ValidationableException: Interface with asValidationException method to convert an error/exception/validation object into a validation exception.