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

js-errors

v0.0.3

Published

General javascript errors generator

Readme

js-errors NPM version Build Status Dependency Status Coverage percentage

General javascript errors generator

javascript errors with

  1. Domain
    The same as prefix, errors with prefix can be more recognizable
  2. Predefined errors
    Predefined errors are standard errors of js-errors and will be enriched
  3. I18n
    Error messages vary with locales
  4. Customization
    Error folder can be specified to customize errors
  5. Unification Error code of each error can never be changed, so it can be exchangable through projects, no need to define errors for every project

Installation

$ npm install --save js-errors

Usage

//Error generation
var BaseError = require('js-errors').error;

//Error definition
var i18n = require('js-errors').i18n;
var errorMessages = i18n.get(pathOfErrorMessagesDefined);

New An Error

var error = new BaseError({
      errors: ['user', 'not', 'found'],    //Sequential Error Description
      prefix: 'java:',                     //Prefix for Messages
      code: 404,                           //Numeric value for this error
      message: 'User is not found!',       //Customized Error Messsage
      locale: 'en-US',                     //Locale for errors
      i18n: i18n.get(dir)                  //Customized error definition directory
    });
//error.name => "UserNotFound"
//error.code => 404
//error.message => "java:User is not found!"
//error.restify() => { code: 404, message: "js:hello", name: 'UserNotFound'}

Throw An Error

throw error;

Error Messages

  • js-errors predefined some errors as standard errors
  • errors can be customized by folders or by generation
  • can also be replaced by providing locales folder when creating a generator

License

MIT © calidion