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

custom-error-factory

v1.0.1

Published

A factory to create instantiable custom error objects, extending native error types

Downloads

5

Readme

Custom Error Factory

custom-error-factory is an open source module that exposes a factory function to create instantiable custom error classes, extending native error types.

Using custom error classes allows you to store more information,a nd in a clearer way, than in a standard object. This can make custom errors easier to retrieve and analyse once being logged.

Install with the command npm install custom-error-factory

Creating a custom error class

You can create a custom error type using the function customErrorFactory, which returns the constructor of the custom error class.

//built-in error class to inherit from
var type = TypeError;

//custom error name
var name = 'Invalid_Delay_Granularity_Error';

//custom error message (can be overwritten at the instance level)
var defaultMessage = 'This is not a recognized time period. Try: \'seconds\', \'minutes\', \'hours\'.';

var InvalidDelayGranularityError = customErrorFactory(type,
	name,
	defaultMessage);

You can then create an instance of this custom error class:

var e = new InvalidDelayGranularityHRError();

You can pass additional properties to the constructor:

var obj = {
	foo: 'bar'
};

var e = new InvalidDelayGranularityError(obj);

You can also overwrite the default message:

var e = new InvalidDelayGranularityHRError('overwritten message');

And also overwrite the default message and pass additional properties at the same time:

var obj = {
	foo: 'bar'
};

var e = new InvalidDelayGranularityHRError(obj, 'overwritten message');

Tests

The test spec is in /test/test.spec.js, and the test suite is jasmine-node, which you can install by running npm install -g jasmine-node

You can run the tests with the commands jasmine-node test or npm run test

To do

Perhaps some integration with an error logging library? This would be a good way to leverage the extra information that can be stored in a custom error object.

Thank you for reading this far. If you have any bugs to report or improvements to suggest you can send me an email at [email protected].