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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@cafeine-software/errorunstack

v1.1.6

Published

A nice display of the error stack in your CLI

Readme

Error Unstack

Node

A nice display of the error stack in your CLI

InstallationUsageDocumentationLicenseContactSupport

Description

Error chains with cause look cool on paper, but unpacking them in the console is a nightmare. errorUnstack takes your nested errors and transforms them into a formatted, readable, and structured display. File positions, clear messages, attached data, colors... everything you need to debug without the headache.

Installation

npm i @cafeine-software/errorunstack

Usage

Minimalist

import { displayErrorStack } from '@cafeine-software/errorunstack';

function bar() {
    throw new Error("Bar function failed");
}

function foo() {
    try {
        bar()
    }
    catch (err) {
        throw new Error("Bar call failed", { cause: err });
    }
}

try {
    foo();
}
catch (err) {
    displayErrorStack(err, "Error in main execution");
}

Custom data

You can add custom data for debug purpose by filling the data argument of the Error object.

import { displayErrorStack } from '@cafeine-software/errorunstack';

function bar() {throw new Error("Bar function failed");}

function foo(level) {

    try { bar();}
    catch (err) {
        const error = new Error("Bar call failed", { cause: err });
        error.data = {
            level: level,
            timestamp: [43,56,"toto","titi"],
            object: {nested: {value: 123}}
        }
        throw error;
    }

}

try {foo(42);}
catch (error) {
    displayErrorStack(error, "Error in main execution");
}

Special key : method

You can specify a method key in you custom data object, it will display beside code coordinate (line:col) the method name


function bar() {

    const error = new Error("Bar function failed");
    error.data = {
        method: "bar"
    }
    throw error;
}

function foo(level) {

    try { bar(); }
    catch (err) {
        const error = new Error("Bar call failed", { cause: err });
        error.data = {
            level: level,
            timestamp: [43, 56, "toto", "titi"],
            object: { nested: { value: 123 } },
            method: "foo"
        }
        throw error;
    }

}

try { foo(42); }
catch (error) {
    displayErrorStack(error, "Error in main execution");
}

Documentation

The package export two methods extractErrorChain and displayErrorStack

extractErrorChain(error)

Extract the error chain from an Error object

Parameters

| Parameter | Type | Default | Description | |-----------|------|---------|-------------| | error | Error | - | The error (contaning causes stack) |

Returns

Array<ErrorEntry> - An array containing object describing each error

displayErrorStack

Display a formatted error stack in the console

Parameters

| Parameter | Type | Default | Description | |-----------|------|---------|-------------| | error | Error | - | The error (contaning causes stack) | | title | String | An error occurred | Title to display above the error stack |

Returns

Void

Types

ErrorEntry

| Parameter | Type | Default | Description | |-----------|------|---------|-------------| | message | String | - | The error message | | file | String | - | The file where the error occurred | | line | Number | - | The line where the error occurred | | col | Number | - | The col where the error occurred | | data | Object | - | Custom data added to the error |

License

Contact

Developed by Quentin Lamamy.

Support