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

@deployagram/msw

v1.0.0

Published

Records HTTP calls intercepted by MSW (Mock Service Worker) and sends them to the Deployagram Collector, in the same format as the Deployagram HTTP Proxy. Use it instead of the Proxy when tests stub HTTP with MSW.

Readme

@deployagram/msw

Records HTTP calls that MSW intercepts, and sends them to the Deployagram Collector. It is the alternative to the Deployagram HTTP Proxy for tests that stub HTTP with MSW: the calls never leave the test process, so there is no Proxy to route them through.

import { setupServer } from 'msw/node';
import { recordHttp } from '@deployagram/msw';
import { DiagramLoggerClient } from '@deployagram/logger-client';

const server = setupServer(/* your handlers */);
server.listen({ onUnhandledFrame: 'error' });

const recorder = recordHttp(server, {
  logger: new DiagramLoggerClient({ baseUrl: 'http://localhost:1152' }),
  caller: 'EmailClient',
  callees: [{ name: 'Emailer', urlPrefix: 'http://localhost:9001' }],
});

// After each test, before marking the test's end:
await recorder.flush();

Each request and response becomes one log entry in the same format the Proxy writes, so the Collector and Deployagram Cloud read them in the same way.

Differences from the Proxy

  • The entries are timestamped when the event happens, not by the Collector.
  • Repeated header values are joined with commas, not kept as separate values.
  • A failure to reach the Collector is reported with a warning, and does not fail the test.

Testing

npm test

The tests use MSW and a logger that keeps entries in memory. They need no Collector.