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

@nexusdi/node

v0.4.0-rc.1

Published

Eliminate manual scope passing by binding NexusDI scopes to the Node.js async context.

Readme

@nexusdi/node

npm license

Eliminate manual scope passing by binding NexusDI scopes to the Node.js async context.

Server environments require request-scoped dependencies: objects created when a request arrives and disposed when it settles. Manually passing these scope objects through every function in a call chain creates brittle, cluttered code.

@nexusdi/node solves this by leveraging AsyncLocalStorage. It tracks the active scope across asynchronous execution paths, allowing your application logic to retrieve the current scope without explicit parameters.

Key Features

The library provides specialized infrastructure for Node.js environments:

  • Automatic Context Tracking: scopes.run() binds a scope to the current async context.
  • Transparent Access: scopes.current() retrieves the active scope anywhere in the execution path.
  • Single Process Instance: One nodeScopes() instance serves every container in the process.
  • Platform Isolation: This package contains all Node-specific logic to keep @nexusdi/core platform-agnostic.

Installation

0.4 is a release candidate on the npm next tag. Install every @nexusdi package from next so their versions match. Without @next, npm installs core 0.3 and stops with a peer conflict.

npm install @nexusdi/node@next @nexusdi/core@next

Quick Example

The following example demonstrates how a deep function can access a scoped dependency without receiving the scope as an argument.

import { Nexus, Token, provide } from '@nexusdi/core';
import { nodeScopes } from '@nexusdi/node';

interface IShipLog {
  readonly lines: string[];
}
class ShipLog implements IShipLog {
  readonly lines: string[] = [];
}
const SHIP_LOG = new Token<IShipLog>('ShipLog');
const scopes = nodeScopes();

// This function is called deep in the app logic, with no scope parameter.
async function record(line: string) {
  await Promise.resolve(); // Simulate async work
  scopes.current()?.get(SHIP_LOG).lines.push(line);
}

await using ship = await Nexus.create([
  provide(SHIP_LOG, { useClass: ShipLog, lifetime: 'scoped' }),
]);

await using shuttle = await ship.createScope();
await scopes.run(shuttle, () => record('survey-7 launched'));

shuttle.get(SHIP_LOG).lines; // -> ['survey-7 launched']
scopes.current(); // -> undefined

In a server, return await scopes.run(...) from the handler, so await using keeps the scope open until the handler finishes. Declare the container with const ship: await using at the top level of a module disposes it as soon as the module finishes loading.

Documentation

License

MIT