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/testing

v0.4.0-rc.1

Published

Simplify integration tests with type-safe provider overrides.

Readme

@nexusdi/testing

npm license

Simplify integration tests with type-safe provider overrides.

Integration testing often becomes a burden when components depend on complex services like databases or external APIs. Setting up a full production environment for every test is slow and fragile, while manually mocking every dependency leads to tests that pass even when the real application graph is broken.

@nexusdi/testing solves this by allowing you to instantiate your real production module graph and surgically swap specific providers for fakes or stubs.

Key Features

The library provides high-fidelity simulation of your dependency graph.

  • Real Graph Validation: createTestingContainer runs the full NexusDI compiler to ensure overrides do not break the graph.
  • Precision Overrides: Replace single providers with override() or entire modules with overrideModule(module, stub).
  • Lifetime Preservation: An override maintains the lifetime of the original binding it replaces.
  • Immutable Builders: Every .override() call returns a new builder for shared base configurations.

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 -D @nexusdi/testing@next @nexusdi/core@next

Quick Example

import { Token, defineModule, provide } from '@nexusdi/core';
import { createTestingContainer } from '@nexusdi/testing';

interface INavCharts {
  plot(to: string): string;
}

class SubspaceCharts implements INavCharts {
  plot(): string {
    throw new Error('no subspace link in tests');
  }
}

const NAV_CHARTS = new Token<INavCharts>('NavCharts');
const Engineering = defineModule({
  name: 'Engineering',
  providers: [provide(NAV_CHARTS, { useClass: SubspaceCharts })],
  exports: [NAV_CHARTS],
});

const fakeCharts: INavCharts = { plot: () => 'loopback' };

await using ship = await createTestingContainer(Engineering)
  .override(NAV_CHARTS, { useValue: fakeCharts })
  .create();

ship.get(NAV_CHARTS).plot('anywhere'); // -> 'loopback'

Documentation

License

MIT