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

@fetchproxy/test-helpers

v1.4.0

Published

Vitest mock helpers for @fetchproxy/server — drop-in FetchproxyServer mock that captures constructor opts and exposes spy-able request/fetch/captureRequestHeader/bridgeHealth methods.

Readme

@fetchproxy/test-helpers

Vitest mock utilities for @fetchproxy/server. Drop-in FetchproxyServer replacement that captures constructor options and exposes spy-able lifecycle + data methods — so you can assert what your FetchproxyTransport adapter is passing to the underlying server without spinning up a real WebSocket.

Why

Every downstream *-mcp repo that wraps @fetchproxy/server ends up re-implementing the same module-scoped ctorCalls array and ad-hoc MockFetchproxyServer class to verify it's threading options (keepAliveIntervalMs, bridgeReviveDelayMs, fetchTimeoutMs, …) through to the constructor. The keep-alive cohort of 0.8.1 PRs (zillow#87, redfin#77, compass#72, homes#49, onehome#46, opentable#57, resy#38) all carried near-identical copies of the same ~25 lines. This package hoists it once.

Install

npm install --save-dev @fetchproxy/test-helpers

vitest (>=1.0) and @fetchproxy/server are peer dependencies.

Usage

import { describe, it, expect, beforeEach, vi } from 'vitest';
import { createMockFetchproxyServer } from '@fetchproxy/test-helpers';

// Module-scoped so vi.mock's hoisted factory can close over it.
const helpers = createMockFetchproxyServer();

vi.mock('@fetchproxy/server', async () => {
  return { FetchproxyServer: helpers.MockServer };
});

beforeEach(() => helpers.reset());

it('passes keepAliveIntervalMs through to FetchproxyServer', async () => {
  const { FetchproxyTransport } = await import('../src/transport-fetchproxy.js');
  new FetchproxyTransport({ version: '0.0.0-test' });

  expect(helpers.getLastCtorOpts()?.keepAliveIntervalMs).toBe(25_000);
});

it('captures the Authorization header on the right URL', async () => {
  const { FetchproxyTransport } = await import('../src/transport-fetchproxy.js');
  const t = new FetchproxyTransport({ version: '0.0.0-test' });

  // Override the default empty-string stub on a specific test.
  const opts = helpers.getLastCtorOpts();
  // ...assert captureHeaders, then exercise:
  // (the MockServer instance's captureRequestHeader spy is on the
  // instance the transport just created; reach it via your transport's
  // public seams or override the spy before the call.)
});

API

createMockFetchproxyServer()

Returns { MockServer, ctorCalls, getLastCtorOpts, reset }:

| Field | Type | What it does | | ------------------- | ----------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | MockServer | class | Drop into the vi.mock('@fetchproxy/server', ...) factory as FetchproxyServer. Constructed with new MockServer(opts). | | ctorCalls | FetchproxyServerOpts[] | Live, append-only list of every new MockServer(...) call's opts. Referentially stable across reset() (mutated in place). | | getLastCtorOpts() | () => FetchproxyServerOpts \| undefined | The most recent ctor opts; undefined when none. | | reset() | () => void | Clears ctorCalls in place and .mockClear()s every previously-created instance's spy methods. Call from beforeEach. |

MockFetchproxyServerInstance

Each new MockServer(opts) instance has these vi.fn()-backed spies (default stubs return undefined / empty string; tests override per case via mockResolvedValue / mockImplementation):

  • listen() / close() — lifecycle no-ops.
  • request() / fetch() — data verbs.
  • captureRequestHeader() — header-capture verb.
  • bridgeHealth() — health snapshot.

License

MIT.