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

errors-factory

v1.0.1

Published

Define your errors in a dedicated file, then use them by their code

Downloads

3

Readme

ErrorsFactory

Define your errors in a dedicated file, then use them by their code

npm node Travis Coveralls

Overview

ErrorsFactory allows defining a set of error in a centralized place (a JSON file, for instance) to, then, be used anywhere in your app. It's especially useful when an error is used multiple times, updating its content will be done once.

Looking at the logs will provide you the message and the code identifying the error

Usage

Install from npm

npm install errors-factory

Require in your code

const ErrorsFactory = require('errors-factory');

Manage your errors in an Array with Objects providing a code and message properties

const errorDefinitions = [{
    code: 'ERR_001',
    message: '1st error'
}, {
    code: 'ERR_002',
    message: '2nd error'
}];

Pass the error definitions to the factory

const errors = new ErrorsFactory(errorDefinitions);

Get the errors by its code

throw errors.ERR_001; // Equivalent to new Error('ERR_001 - 1st error');

Example

// errors.json
[{
    "code": "ERR_APP_XXX",
    "message": "Not yet implemented"
}, {
    "code": "ERR_APP_001",
    "message": "bar shall not be null"
}]
// app.js
const ErrorsFactory = require('errors-factory');
const errors = new ErrorsFactory(require('./errors.json'));

function foo(bar) {
    if (bar === null) {
        throw errors.ERR_APP_001; // Equivalent to new Error('ERR_APP_001 - bar shall not be null');
    }

    throw errors.ERR_APP_XXX; // Equivalent to new Error('ERR_APP_XXX - Not yet implemented');
}