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 🙏

© 2024 – Pkg Stats / Ryan Hefner

errata

v0.0.6

Published

[![Build Status](https://travis-ci.org/kjdelisle/errata.svg?branch=master)](https://travis-ci.org/kjdelisle/errata)

Downloads

7

Readme

Errata

Build Status

Easily create custom error types for better flow control and logging.

Usage

Create your error constructor, and throw with it:

// Create an error prototype
var errata = require('errata');
var ImportantError = errata.create('ImportantError', 'IMPORTANT');

// throw it
throw new ImportantError('OH NOES!');

Get stack traces that include your custom error name:

ImportantError: OH NOES!
    at eval (eval at <anonymous> (/app/index.js:715:19), <anonymous>:12:11)
    at GeneratorFunctionPrototype.next (native)
    at /app/index.js:573:32

Pass in a function as part of the error definition to cut down on boilerplate:

var errata = require("errata");
var os = require('os');
var util = require('util');

var RolloutError = errata.create('RolloutError', 'MAYBE', function(obj) {
    if (obj instanceof ReallyImportantObject)
        this.severity = 'REALLYBAD';
    else
        this.severity = 'NOTSOBAD';
    this.message = util.format('Failure of severity %s!%s%s', this.severity,
        os.EOL, this.message);
});

function ReallyImportantObject() {
    // has some important function thingy in it.
}
try {
    throw new RolloutError(new ReallyImportantObject);
} catch (err) {
    console.log(err.stack);
}

API

errata.create(name, [[code], [handler, ...]])

Create a new Error prototype with the given name as its object type. An optional code may be specified so that all instances of the created Error have the default error code. An optional handler function may be provided that takes any remaining parameters in. You may use this function as you see fit to modify the behaviours and properties of the Error object.

You may also call errata(name, [[code], [handler, ...]]) for the same effect.

errata.loadConfig(filepath)

Loads a JSON file that defines a list of custom Errors, and returns an Array of Error constructors.