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

v0.4.0-rc.1

Published

Decouple cross-cutting concerns from your business logic using transparent method wrappers.

Readme

@nexusdi/interceptors

npm license

Decouple cross-cutting concerns from your business logic using transparent method wrappers.

Mixing audit logging, performance tracking, or input validation directly into your services creates bloated classes and violates the single-responsibility principle. When business logic is entangled with infrastructure concerns, services become harder to test and maintain.

@nexusdi/interceptors solves this by providing a plugin for NexusDI that wraps service methods in a proxy layer. This allows you to inject logic (such as result caching or sensitive method auditing) without modifying the service implementation.

Key Features

Interceptors are defined as providers. They must implement an intercept(call, next) method to modify arguments, short-circuit calls, or observe results via tap().

Attachment is highly granular. You can apply interceptors globally, to specific tokens, to an entire class, or to a single method.

Execution relies on transparent proxies. All calls resolved through get() are intercepted, while internal calls via this remain direct.

Technical Specifications. This package is ESM-only and requires matching @next versions for @nexusdi/core to avoid peer dependency conflicts.

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

Quick Example

import { Nexus, Token, provide } from '@nexusdi/core';
import { interceptor, interceptors, tap } from '@nexusdi/interceptors';
import type { Interceptor } from '@nexusdi/interceptors';

interface INavigator {
  plot(to: string): string;
}
class Navigator implements INavigator {
  plot = (to: string) => `course to ${to}`;
}

const NAVIGATOR = new Token<INavigator>('Navigator');
const AUDIT = new Token<Interceptor>('Audit');
const log: string[] = [];

const audit = interceptor(AUDIT, {
  useValue: {
    intercept: (call, next) => {
      log.push(`call ${String(call.method)}`);
      return tap(next, { value: (course) => log.push(`got ${course}`) });
    },
  },
});

const plugins = [interceptors({ register: [audit], global: [AUDIT] })];
const providers = [provide(NAVIGATOR, { useClass: Navigator })];
await using ship = await Nexus.create(providers, { plugins });

ship.get(NAVIGATOR).plot('Vega');
log; // -> ['call plot', 'got course to Vega']

Documentation

License

MIT