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

faulty

v0.1.2

Published

A utility function to create custom error objects

Downloads

10

Readme

faulty

A utility function to create custom error objects in Javascript.

Installation

Install via npm:

% npm install faulty

Usage

var createError = require('faulty');
// => [Function]

var MyError = createError('MyError');
// => [Function: MyError]

MyError.name
// => 'MyError'

var err = new MyError('something bad has just happened');
// => [MyError: something bad has just happened]

err instanceof Error
// => true

err instanceof MyError
// => true

err.name
// => 'MyError'

err.message
// => 'something bad has just happened'

err.stack
// => 'MyError: something bas has just happened\n  at <...stack trace...>'

var err2 = new MyError('another error', { foo: 'bar', baz: 123 });
// => [MyError: another error]

err2.foo
// => 'bar'

err2.baz
// => 'baz'

var WrappedError = createError('WrappedError', function(message, originalError) {
  this.originalError = originalError;
});

var err3 = new WrappedError('see second arg', new Error('foo'))
// => [WrappedError: see second arg]

err3.originalError
// => [Error: foo]

Contributing

Here's a quick guide:

  1. Fork the repo and make install.

  2. Run the tests. We only take pull requests with passing tests, and it's great to know that you have a clean slate: make test.

  3. Add a test for your change. Only refactoring and documentation changes require no new tests. If you are adding functionality or are fixing a bug, we need a test!

  4. Make the test pass.

  5. Push to your fork and submit a pull request.

Licence

Released under The MIT License.