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

@yankeeinlondon/kind-error

v1.0.1

Published

> A better error primitive than what Javascript hands you.

Downloads

135

Readme

Kind Error

A better error primitive than what Javascript hands you.

Usage

  1. Create an Error type with first call to createKindError:

    const InvalidRequest = createKindError("invalid-request", { lib: "foobar" });
  2. Throw an error of this type:

    throw InvalidRequest("oh no!");

    you may optionally adding additional "context" to the error when you throw it:

    throw InvalidRequest("oh no!", { params: [ "foo", "bar"]});

In this example the person catching the error would find params and lib set on the error's "context" property.

Benefits Summary

  1. Context

    As was indicated in our example above we provide a "context" property which is a dictionary of key/value pairs you can defined either at the time you define the error type or at the actual error being thrown.

    Note: if you set the same key both setting up the error type and again when throwing the error, the latter key/value will overwrite the former.

  2. Kind

    When you create you're error with the call to createKindError(kind, ctx) the first parameter will define the "kind" of error this is. By the time your error is thrown, the "kind" and "name" properties of your error will be set based on this. The "kind" property is a dasherized version of the kind and the "name" property is a PascalCase version of the kind.

  3. Type Support When Catching Errors

    Every attempt is made to preserve types during error creation but when catching errors we have provided the isKindError(val) type guard which will bring back good type support to tap into the "context", "type", "stack" and "kind" properties.

  4. Error Stack

    Javascript return a string for a stack trace and requires us to parse it. When you use a KindError you will be provided a stackTrace property which is an array of stack items, where a stack item is:

    type StackItem = {
      file: string | undefined;
      function?: string;
      args?: any[];
      col?: number;
      line?: number;
      raw?: string;
    }

    Finally, a file, line, and col property are directly exposed for the top item in the stack.