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

tiawa

v1.1.1

Published

Preserve the full stack trace on error when using async methods

Downloads

2

Readme

tiawa

Long stack traces for async methods.

Background

a major headache of node.js is the difficulty in obtaining a full stack trace when errors are thrown within asynchronous methods, making spotting the source of the error very difficult when dealing with highly reused methods. tiawa makes handling this problem simpler by throwing a new error with a stack trace modified to contain the original error. this still requires the programmer to add an explicit 'catch' to each asynchronous method, but aleviates the burden of manually logging and re-throwing a new error.

Install

npm install --save tiawa

Import

const tiawa = require('tiawa')

Usage

Tiawa can be used in two ways, first, to grab the response/error so that it can be processed in the current call stack:

  const result = await tiawa(
    myAsyncMethod(x, y, z)
  );

  if (result.error !== null) {
    // Either handle error, or re-throw
    throw result.error;
  }

  console.log(result.result);

Or alternatively, to round up the full stack trace, and re-throw:

await someAsyncMethod(x, y, z).catch(e => tiawa(e));

tiawa will throw a new error and augment the existing stack trace with the current position in the call stack. no overhead, dead simple. fine for production use.

nested calls to async methods which use tiawa will preserve the entire call stack so that the programmer knows the full origin of the async call that's failing.