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

standard-error

v1.1.0

Published

Tiny library that simplifies subclassing and inheriting from Error while keeping the correct name and stack. Also supports constructing from an object of properties. Saves you from boilerplate.

Downloads

198,484

Readme

StandardError.js

![NPM version][npm-badge] [npm-badge]: https://badge.fury.io/js/standard-error.png

StandardError.js is a tiny JavaScript library that simplifies creating subclasses of Error for custom error classes with the correct name and stack property. Saves you from writing a few lines of boilerplate.

Tour

  • Create custom error classes and add new behavior to them while keeping the standard Error behavior in tact.
  • Add extra properties to the error by just passing in an object.
  • StandardError.js sets the error's stack trace correctly, even if your error class subclasses/inherits from StandardError.
    Just inheriting from Error with Object.create breaks the stack trace.
  • Every StandardError instance is also an instance of Error.
  • Serializes all expected properties when passing it to JSON.stringify.
    Did you know that the default Error object serializes to an empty object ({})?
  • Works both in Node.js and browsers and sets the stack trace via Error.captureStackTrace where available.

Installing

npm install standard-error

Using

Just require StandardError.js and either use it directly or inherit from it for your custom error class.

Throwing StandardError

Like Error, StandardError takes a message argument, but in addition to that, you may give it an object with other properties to be set:

var StandardError = require("standard-error")
throw new StandardError("Not Found", {code: 404})

The thrown instance of StandardError will then have both the message and the code property.
It'll also also have a name property set to "StandardError".

You can skip the explicit message argument and give everything as an object of properties:

new StandardError({message: "Not Found", code: 404})

Note: All properties besides stack will be enumerable for easier serialization with JSON.stringify. That includes the name property which will be set from the constructor's name (defaults to "StandardError").

Subclassing and inheriting from StandardError

The real benefit of StandardError.js comes from subclassing it to create new error classes and adding custom behavior to them.

Let's create an HttpError that we can instantiate with the HTTP status code (new HttpError(404)) and have it set the message automatically based on that:

var Http = require("http")
var StandardError = require("standard-error")

function HttpError(code, msg) {
  StandardError.call(this, msg || Http.STATUS_CODES[code], {code: code})
}

HttpError.prototype = Object.create(StandardError.prototype, {
  constructor: {value: HttpError, configurable: true, writable: true}
})

Note that you must set the constructor property like in the above example. First, that's the proper way to subclass in JavaScript and second, StandardError.js depends on that to know which functions to skip in the stack trace.

Name

StandardError.js finds out the name (err.name) of your subclassed error from its constructor function. However, if you minify your code, you can also set or change it explicitly:

ChildError.prototype.name = "FallacyError"

Adding behavior to your subclass of StandardError

Now that you've inherited, you can, for example, customize stringifying by overwriting toString on your subclass. To get new HttpError(404) to print itself as 404 Not Found:

HttpError.prototype.toString = function() {
  return this.code + " " + this.message
}

License

StandardError.js is released under a Lesser GNU Affero General Public License, which in summary means:

  • You can use this program for no cost.
  • You can use this program for both personal and commercial reasons.
  • You do not have to share your own program's code which uses this program.
  • You have to share modifications (e.g. bug-fixes) you've made to this program.

For more convoluted language, see the LICENSE file.

About

Andri Möll typed this and the code.
Monday Calendar supported the engineering work.

If you find StandardError.js needs improving, please don't hesitate to type to me now at [email protected] or create an issue online.