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

exceptions-with-cause

v2.2.2

Published

Simple utility to provide errors with causes

Downloads

18

Readme

exceptions-with-cause

npm npm type definitions npm modules type npm bundle size

What?

The exceptions-with-cause package is a simple utility that provides java-style causes for errors in javascript. This is useful when catching and throwing errors upwards where you still want to keep what caused the original error.

Why?

Let's say you have a function performTask which when you run it throws this error:

TypeError: Cannot convert undefined or null to object
    at Function.entries (<anonymous>)
    at performTask (/Users/user/project/index.js:5:10)
    at main (/Users/user/project/index.js:9:3)

This error can be useful in the sense that it is low level, it tells you exactly what went wrong and where, but unfortunately leaves out the larger context of when and why the function was called.

You could try and remedy this by catching any error thrown by performTask and attach additional information there.

try {
  performTask();
}
catch (error) {
  throw new Error(`Request failed because of error in "performTask": ${error.message}`);
}

When running this we get:

Error: Request failed because of error in "performTask": Cannot convert undefined or null to object
    at main (/Users/user/project/index.js:13:11)
    at Object.<anonymous> (/Users/user/project/index.js:17:1)

With this we can quickly see the program was trying to make a request when it was calling performTask, however we lose the stack trace from before making it much harder to find the actual cause of the error.

With the exceptions-with-cause package we can get the best of both worlds by attaching a cause to our error:

Error: Request failed because of error in "performTask"
    at main (/Users/user/project/index.js:13:11)
    at Object.<anonymous> (/Users/user/project/index.js:17:1)
Caused by: TypeError: Cannot convert undefined or null to object
    at Function.entries (<anonymous>)
    at performTask (/Users/user/project/index.js:5:10)
    at main (/Users/user/project/index.js:9:3)

How?

Like this:

import Exception from 'exceptions-with-cause'; // or use require if using commonjs

try {
  // Something goes wrong in here, for example:
  JSON.parse(undefined);
}
catch (error) {
  throw new Exception('Something descriptive of what the code was doing', error);
}

Which will result in this error:

Exception: Something descriptive of what the code was doing
    at Object.<anonymous> (/Users/user/project/index.js:8:9)
Caused by: SyntaxError: Unexpected token u in JSON at position 0
    at JSON.parse (<anonymous>)
    at Object.<anonymous> (/Users/user/project/index.js:5:8)

Retrieving the cause

It is also possible to retrieve the cause object from an exception if needed, like this:

const ex = new Exception('Error', { example: 123 });

const cause = Exception.cause(ex); // Will return { example: 123 }