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

@spinejs/cls

v0.1.5

Published

Per-request context for SpineJS via AsyncLocalStorage (CLS).

Readme

@spinejs/cls

Per-request context for SpineJS, backed by a single AsyncLocalStorage exposed as an injectable singleton ClsService. Open a scope per request; deep services read the current request's data via cls.get() without threading a context object through every signature. See ADR 0003.

Quick start

Open a scope at the edge (one per request/dispatch/job), then read it anywhere below.

import { Injectable } from "@spinejs/core";
import { ClsService } from "@spinejs/cls";

// At the edge — seed the scope for the async call chain:
@Injectable({ inject: [ClsService] })
export class RequestHandler {
  constructor(private readonly cls: ClsService<{ userId: string }>) {}

  handle(userId: string) {
    return this.cls.run({ userId }, () => this.doWork());
  }
  private doWork() {
    /* deep call chain … */
  }
}

// Anywhere deeper — same singleton, reads the current scope:
@Injectable({ inject: [ClsService] })
export class AuditService {
  constructor(private readonly cls: ClsService<{ userId: string }>) {}
  record(action: string) {
    const userId = this.cls.get("userId"); // no context object threaded in
    /* … */
  }
}

Two concurrent run()s get isolated stores — the binding is to the async execution context, not to a shared variable.

With a gateway

ClsInterceptor opens a scope around every dispatch. Register it via the transport module's configure({ interceptors }), seeding the store from the context:

new ClsInterceptor(cls, (ctx) => ({ userId: ctx.session.userId }));

Reference

  • ClsService<T>run(seed, fn) opens a scope and runs fn inside it; get(key) / set(key, value) read/write the current store (set throws outside a scope); active is true inside a run().
  • ClsModule — provides ClsService as a singleton.
  • ClsInterceptor — a GatewayInterceptor that wraps each dispatch in a scope.

Full docs

apps/docs-site/docs/extensions/cls