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

ex-error

v1.0.2

Published

Extendible error wrapper for NodeJS and browser

Downloads

4

Readme

Ex-Error Build Status Coverage Status

An extendible error class for creating custom error.

Why Use This Package?

Custom error object is quite useful if you need to filter specific error type. You can read this article to get more context why custom error is very useful.

Example:

// With standard error object
try {
  // Normally one will throw an error
  throw new Error('Error on auth');
} catch (err) {
  // catch error in here
}

// With custom error object
try {
  throw new AuthError('Your password is missing');
} catch (err) {
  if (err instanceof AuthError) {
    // process error for AuthError
  } else {
    // process error for other than AuthError
  }
}

Using Package

import exError from 'ex-error';
// or
const exError = require('ex-error');

// creating default error object from standard Error class
const DefaultError = exError();

try {
  // adding error message
  throw new DefaultError('Error using default error');
} catch (e) {
  console.log(e.message); // -> 'Error using default error'
  console.log(e.name); // -> 'Error'
  console.log(e instanceof DefaultError); // -> true
}

// creating custom error object
const CustomError = exError('CustomError');

try {
  // adding error message and custom properties
  throw new CustomError('Custom error', {
    code: 500,
    otherMessage: 'other message'
  });
} catch (e) {
  console.log(e.message); // -> 'Custom error'
  console.log(e.name); // -> 'CustomError'
  console.log(e instanceof CustomError); // -> true
  console.log(e.code); // -> 500
  console.log(e.otherMessage); // -> 'other message'
}

One can also use it as class extension

import exError from 'ex-error';

const CustomError = exError('CustomError');

class UseCustomError extends CustomError {}

try {
  // adding error message and custom properties
  throw new UseCustomError('Custom error', {
    code: 500,
    otherMessage: 'other message'
  });
} catch (e) {
  console.log(e.message); // -> 'Custom error'
  console.log(e.name); // -> 'CustomError'
  console.log(e instanceof CustomError); // -> true
  console.log(e.code); // -> 500
  console.log(e.otherMessage); // -> 'other message'
}

License

Licensed under the MIT License. You can find a copy of it in LICENSE.