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

v4.0.18

Published

Lightweight context propagation for JavaScript and TypeScript. Create a scoped storage object, run code inside it, and read the active value anywhere down the call stack - without depending on React.

Readme

Context 🪆

Lightweight context propagation for JavaScript and TypeScript. Create a scoped storage object, run code inside it, and read the active value anywhere down the call stack - without depending on React.

  • createContext(defaultValue?) – simplest option with a single value per run.
  • createCascade(initializer?) – merges parent and child context objects, ideal for layered data.
  • bind – capture context for later execution (useful with async callbacks).

Installation

npm i context

createContext

Create an isolated context with an optional default value used outside of a running scope.

import { createContext } from 'context';

const requestContext = createContext({ requestId: undefined });

function handleRequest(requestId) {
  return requestContext.run({ requestId }, () => {
    logRequest();
    return doWork();
  });
}

function logRequest() {
  // Inside run → current context value
  console.log(requestContext.use().requestId);
}

API:

  • run(value, callback) – activates the context for the callback. Nested runs temporarily override the value and restore it afterwards.
  • use() – returns the current value or the default when no context is active.
  • useX(message?) – like use, but throws if called outside of run, ignoring any default value.

createCascade

createCascade composes context objects instead of replacing them. Each run merges the current value with the parent context, so shared properties flow down while children can add or override keys.

import { createCascade } from 'context';

const userContext = createCascade();

userContext.run({ user: { id: 5, name: 'Ada' } }, () => {
  // child run inherits id/name and adds role
  userContext.run({ user: { role: 'admin' } }, () => {
    const ctx = userContext.use();
    // ctx.user => { id: 5, name: 'Ada', role: 'admin' }
  });
});

API additions:

  • use() / useX(message?) – return the merged object for the current layer.
  • run(value, callback) – merges value into the parent context without passing arguments to callback.
  • bind(value, callback) – returns a function that executes callback inside a context seeded with value, preserving arguments when invoked later.

TypeScript

Both factories are fully typed. Annotate your contexts for stricter checks:

const settings = createContext<{ locale: string }>();
const session = createCascade<{ user?: { id: string } }>();

Notes

  • Context is synchronous by design; reading it after an async boundary requires bind or wrapping the async call inside run.
  • Each run call leaves the parent context untouched once the callback completes.