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

nested-error

v1.0.0

Published

An Error class useful for wrapping an exception to get a better stack trace associated with it

Downloads

30

Readme

NestedError

NestedError is an Error class useful for wrapping another Error to get a better stack trace associated with it.

This can be very helpful, especially when the original Error is created close to node's internal event loop.

Usage

First, install NestedError: npm install nested-error

Then make use of it like in this illustrative example:

var net = require('net');
var NestedError = require('nested-error');

// This function is our program:
function listen(callback) {
  // Connect to a nonexistent UNIX domain socket to
  // cause an error in the net module:
  var server = net.connect({ "path": "nonexistent" });

  server.on('error', function (err) {
    // Wrap the error message we get in a NestedError
    // to attach a stack trace that goes here
    callback(new NestedError(err));
  });
}


// This should give an error callback
listen(function (err) {
  if (err) {
    // Write out both stack traces for comparison:
    console.error(err.stack);
    console.error("\nCompare to inner exception:");
    console.error(err.innerException.stack);
    console.error("\nConclude that NestedError lets you debug easier :)");
  }
});

This program will output the stack traces for both the error object we got from node's net module and the NestedError we created. The NestedError gives a much better context to be able to debug the problem.