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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@chilangolabs/api-errors

v1.0.0

Published

Error objects that are designed to be easily handled by @chilangolabs/api error handling middleware and surface useful status codes

Downloads

7

Readme

@chilangolabs/api-errors

Description

Provides error class that should be thrown when you want to surface specific error codes via the api. CLIENT_ERROR & SERVER_ERROR and it's subclasses all extend the javascript Error object and so include stack traces to where the error was created, which makes debugging failure responses much easier. CLIENT_ERROR & SERVER_ERROR contains a status and a message, which are both returned to the client by the @chilangolabs/api error handling middleware.

Errors provided

Client Errors

require('@chilangolabs/api-errors/client')

  • CLIENT_ERROR - Generic API error, constructed with both a status message, all following errors extend this error
  • CLIENT_BAD_REQUEST - Status set to 400 and has a default message that can be overridden
  • CLIENT_UNAUTHORIZED - Status set to 401 and has a default message that can be overridden
  • CLIENT_INVALID_TOKEN - Status set to 400 and has a default message that can be overridden
  • CLIENT_FORBIDDEN - Status set to 403 and has a default message that can be overridden
  • NOT_FOUND - Status set to 404 and has a default message that can be overridden

Server Errors

require('@chilangolabs/api-errors')

  • SERVER_ERROR - Generic API error, constructed with both a status message, all following errors extend this error
  • DB_ERROR - Status set to 500 and has a default message that can be overridden
  • S3_ERROR - Status set to 500 and has a default message that can be overridden

Bot Errors

require('@chilangolabs/api-errors/bot')

  • MESSENGER_ERROR - Status set to 500 and has a default message that can be overridden
  • TELEGRAM_ERROR - Status set to 500 and has a default message that can be overridden
  • WHATSAPP_ERROR - Status set to 500 and has a default message that can be overridden

Communication Errors

require('@chilangolabs/api-errors/communication')

  • FIREBASE_ERROR - Status set to 500 and has a default message that can be overridden
  • SENDGRID_ERROR - Status set to 500 and has a default message that can be overridden
  • SES_ERROR - Status set to 500 and has a default message that can be overridden
  • TWILIO_ERROR - Status set to 500 and has a default message that can be overridden

Payments Errors

require('@chilangolabs/api-errors/payment')

  • CONEKTA_ERROR - Status set to 500 and has a default message that can be overridden
  • OPENPAY_ERROR - Status set to 500 and has a default message that can be overridden
  • PAYPAL_ERROR - Status set to 500 and has a default message that can be overridden
  • STRIPE_ERROR - Status set to 500 and has a default message that can be overridden

Usage Examples:

Return a 500 error when a prisma call fails

const { SERVER_ERROR } = require('@chilangolabs/api-errors');

try {
  const allUsers: User[] = await prisma.users();
} catch (e) {
  throw new SERVER_ERROR();
}