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

context-handle

v1.0.0

Published

A tiny, type-safe wrapper around Node's AsyncLocalStorage for dynamic scoping and dependency injection.

Readme

Context Handle

A tiny, type-safe wrapper around Node's AsyncLocalStorage for dynamic scoping / dependency injection (using the service provider pattern), similar to React Context, but works in any environment where AsyncLocalStorage is supported.

Install

pnpm add context-handle
# or
npm install context-handle
# or
yarn add context-handle

Requires Node.js 18 or later.

Example

A common use case is propagating a database transaction so that any helper called within a unit of work participates in the same transaction, without passing a tx argument everywhere.

import { createContextHandle } from "context-handle";

const transactionContext = createContextHandle<Transaction>("Transaction");

const findUser = (id: string) => {
  const tx = transactionContext.get();
  return tx.query("SELECT * FROM users WHERE id = $1", [id]);
};

const transferFunds = (from: string, to: string, amount: number) => {
  const tx = transactionContext.get();
  // ...do work using `tx`, calling other helpers like `findUser` freely
};

await db.transaction(async (tx) => {
  await transactionContext.start(tx, async () => {
    await transferFunds("alice", "bob", 100);
  });
});

findUser and transferFunds don't take a transaction parameter — they pull it from the context handle. Any code reachable from the start callback (sync or async) sees the same transaction.

API

createContextHandle<Context>(name)

Creates a new context handle.

  • Context — the type of the value you want to scope. Can be any value except undefined.
  • name: string — used in error messages to identify the handle.
  • Returns a ContextHandle<Context>.

Each call to createContextHandle produces an independent handle. Two handles created with the same name do not share state.

ContextHandle<Context>

start(context, fn)

Runs fn with context available via get(). Returns whatever fn returns (including a Promise).

  • context: Context — the value to scope.
  • fn: (context: Context) => T — the callback in which the context is active. Receives the same context value as a convenience.
  • Returns: the return value of fn.

The context is active for the synchronous body of fn, all async continuations awaited from within it, and any callbacks scheduled (e.g. setTimeout, queueMicrotask) before fn returns. Nested start calls shadow the outer value for the duration of the inner callback; once it returns, the outer value is restored.

get()

Returns the current context value.

  • Returns: Context.
  • Throws: if called outside any active start for this handle.

isSet()

Checks whether a context is currently active for this handle without throwing.

  • Returns: booleantrue inside a start callback, false otherwise.

Useful when behavior should differ based on whether a context is available, rather than failing.