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

n-custom-errors

v4.0.0

Published

Custom errors for Node.js

Downloads

7

Readme

n-custom-errors

Custom errors for Node.js.

Build Status Code Coverage npm version

Features

  • custom errors with name, code and error message.
  • template strings for formatting error messages.
  • helper functions for each registered error:
    • get<errorName>Error()
    • get<errorName>ErrorType()
    • is<errorName>Error()

Setting up

# Add to project
$ npm i n-custom-errors

Usage

// Registering errors:
customErrors.registerError('AccessDenied', 403);
customErrors.registerError('DuplicateObject', 409);
customErrors.registerError('ObjectNotFound', 404, '${objectName} not found');

// Creating custom errors:
let objectNotFoundError = customErrors.getObjectNotFoundError({ objectName: 'user' });
let duplicateObjectError = customErrors.getDuplicateObjectError('The email is not unique');

console.log(objectNotFoundError);
/*
prints => {
  name: 'ObjectNotFoundError',
  message: 'user not found',
  statusCode: 404
}*/
console.log(duplicateObjectError);
/*
prints => {
  name: 'DuplicateObjectError',
  message: 'The email is not unique',
  statusCode: 409
}*/

// Checking that an error is a custom error:
let err = new Error();
let objectNotFoundError = customErrors.getObjectNotFoundError({ objectName: 'user' });
customErrors.isObjectNotFoundError(err)); // returns false
customErrors.isObjectNotFoundError(objectNotFoundError)); // returns true

API

  • registerError(name, statusCode, messageTemplate) Registers a new custom error.

    • name - error name, required, must be an unique. Name must be without Error postfix.
    • statusCode - http status code for error.
    • messageTemplate - template for a message, must contains parameters in the following format: ${objectName} not found. To pass the parameters to the template, parameters must be an object with defined properties: customErrors.getObjectNotFoundError({ objectName: 'user' }). If parameters is a string, than this string will be used in an error message without template: customErrors.getObjectNotFoundError('User with a name user1 not found, please use another filter').
  • isKnownError(err) Returns true if err is a registered custom error, false otherwise.

    • err - error object, required.
  • get<errorName>Error(msg) This function is added automatically when a new custom error is registered. Creates a custom error with message msg, it can be the parameters object if an error is registered with messageTemplate.

    • msg - an error message, required.
  • get<errorName>ErrorType() This function is added automatically when a new custom error is registered. Gets a custom error type.

  • is<errorName>Error(err) This function is added automatically when a new custom error is registered. Returns true if err is a custom error, false otherwise.

    • err - error object, required.

Author

Alexander Mac

License

Licensed under the MIT license.