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

errorlet

v0.2.2

Published

a simple custom error library

Downloads

28

Readme

Errorlet - a simple customer error library

A simple custom error library for you to use more than just an error message string, because a string sometimes just isn't enough.

Install

npm install errorlet

Usage

var errorlet = require('errorlet');

// make a custom error and throw it.
throw errorlet.create({error: 'http_error:not_found', message: 'this is the custom error message', httpCode: 404});

// you can directly raise it as well instead of using throw.
// the stack will be the same as if you call throw.
errorlet.raise({error: 'error_code', message: 'this is the custom error message'});

// you can also do it in async fashion.
// the stack will be the same as if you call throw.
errorlet.raiseAsync({error: 'async_error', message: 'you should see this error in the callback'}, function (err) {
  console.log(err);
});

By default, you can set the name of the error object via error or name key. If you are used to constructing error objects for JSON API, chances are this approach will look familiar to you.

message field can be passed in, or if you leave it out, it will be constructed out of the JSON serialization of the object you passed in.