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

pretty.errors

v0.0.2-b

Published

Just because they are errors doesn't mean they can't be pretty.

Readme

Pretty Errors

Just because they are errors doesn't mean they can't be pretty.

TypeError Screenshot

Installation

    npm install pretty.errors

Usage

throw new PrettyError

Pretty Errors extends the Error class and so it can be thrown as such. However, the Pretty Errors constructor accepts three arguments:

  • Message (String) The message property is the string description of the error.
  • Name (String) The name property is a string label that identifies the error.
  • Code (String) The code property is a string label that identifies the kind of error.

By passing it to the constructor, it automatically assigns it.

Moreover, if you wish to create your own custom errors for your app, you can make it pretty by extending the Pretty Errors class.

Example

    let PrettyErrors = require("pretty.errors");

    ...
    throw new PrettyErrors("Something bad occoured", "Really bad error". 500);
    ...

Throw a specific error

Pretty Errors class has a special static method called throw(). This method accepts an Error class, makes it pretty and exits the process. So, if you need to throw a especific error, you can still make use of all this beauty:

    let PrettyErrors = require("pretty.errors");
    
    try {
        require('url').parse(() => { }); // throws TypeError, since it expected a string
    } catch(e) {
        PrettyErrors.throw(e);
    }

Dependencies

Author