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 🙏

© 2025 – Pkg Stats / Ryan Hefner

stack-context

v1.0.2

Published

_Practical application of [async_hooks](https://nodejs.org/api/async_hooks.html) for glory of contexts_

Readme

Stack-context

Practical application of async_hooks for glory of contexts

Build Status Node version Maintainability

If you are working on

  • database ORM/connection suite
  • request handler - HTTP, WS, AQMP, Thrift, whatever
  • context-based event capturer, like Sentry
  • something else with multiple async handlers

you probably encountered the problem. You need to store an object: transaction, connection, some additional variables or what-is-your-problem. And you need to preserve it through all the calls un userland. That's a pain. You need to control whether they preserve your object, and that's a risk.

But with introduction of async_hooks in node.js (since node 8.1) you can relax and allow users to do their stuff, while you are doing yours - magically.

API of stack-context is similar to React context, so if you know React contexts, you roughly understand how to use it.

Example of usage:

// --- your code
import createContext from 'stack-context'

const transactionContext = createContext()

class DatabaseConnection {
   async transact(fn) {
     const tx = db.createTransaction(this)
     await transactionContext.provide(tx, fn)
     tx.commit()
   }
   
   getTx() {
     return transactionContext.consume()
   }
   
   query() {
     const transaction = this.getTx()
     return transaction
         ? db.query(...arguments, transaction)
         : db.query(...arguments)       
   }
}
//--- some userland code
import {connection} from './dbConnection'

export async function doStuff() {
  connection.transact(async () => {
    assert(this.getTx() instanceof Transaction)
    await db.query(query1)
    await fetch(remoteUrl)
    await db.query(query2)
    assert(this.getTx() instanceof Transaction)
  })
  assert(this.getTx() === undefined)
}