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

zeddy-errors

v1.0.1

Published

Error library for Node

Readme

Zeddy Errors

Zeddy Errors is a simple base class for custom errors/exceptions focused on proper TypeScript typings. There are no differences between errors and exception classes except that errors have by default http status code 500 and exceptions 400.

This library closely follows suggestions written in my upcoming book 'Pragmatic Node.js development: Primer in NestJS'. In short make descriptive error names so the error.message is not needed, and pass additional data to further enrich the error for logging.

Usage

Make a new file which export error definitions as in sample below. Recommended is to have one SharedErrors and one for each part of your application ie. AuthErrors, CacheErrors, UserErrors...

In generic argument you can put the type of data that error will contain.

export const SharedErrors = {
  EntityNotFound: class extends ExceptionBase<{ type: string; id: number }> {},
  JwtTokenMissingBearer: class extends ExceptionBase{},
  IntentionalError: class extends ErrorBase<{ reason: string }> {},
};

You can throw the errors with:

import {SharedErrors} from './app.errors';
//...
throw new SharedErrors.IntentionalError({reason: "Testing errors"});
throw new SharedErrors.JwtTokenMissingBearer();

Example project

Example project can be found on https://github.com/zveljkovic/zeddy-errors-example.