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

@thaparoyal/replayapi

v0.1.4

Published

ReplayAPI SDK for Node.js — Capture HTTP traffic automatically

Readme

@replayapi/node

ReplayAPI SDK for Node.js — Automatically capture outgoing HTTP traffic for replay testing.

Install

npm install @replayapi/node

Quick Start

import { replayApi } from '@replayapi/node'

// Initialize once at app startup
replayApi.init({
  apiKey: process.env.REPLAY_API_KEY!,
  environment: 'staging',
})

// That's it — all http, https, and fetch calls are now captured

Configuration

replayApi.init({
  // Required
  apiKey: 'rp_your_api_key',

  // Optional
  proxyUrl: 'http://localhost:8080',  // Default proxy URL
  environment: 'staging',             // Environment label
  sessionId: 'user-checkout-flow',    // Group related requests

  // Filter what gets captured
  include: ['api.example.com', /\/api\/v\d+\//],
  exclude: ['healthcheck', /\.internal\./],

  // Debug
  debug: true,                        // Enable verbose logging
  disabled: false,                    // Disable without removing code
  timeout: 30000,                     // Proxy request timeout (ms)
})

API

replayApi.init(config)

Initialize the SDK. Patches http.request, https.request, and fetch globally.

replayApi.stop()

Stop capturing and restore original HTTP behavior.

replayApi.isActive()

Returns true if the SDK is currently intercepting traffic.

replayApi.getStats()

const stats = replayApi.getStats()
// { totalCaptured: 42, totalSkipped: 3, totalErrors: 0, startedAt: Date }

How It Works

  1. Your app makes an HTTP request: GET https://api.example.com/users
  2. The SDK rewrites it to: GET http://proxy:8080/users with headers:
    • X-Api-Key: rp_... (your API key)
    • X-Replay-Target: https://api.example.com (original target)
    • X-Replay-Env: staging (environment)
  3. The proxy captures the traffic, forwards to the target, returns the response
  4. Your app receives the response as if the proxy wasn't there

Supported

  • Node.js 18+ (native fetch support)
  • http.request / http.get
  • https.request / https.get
  • globalThis.fetch
  • Libraries that use these under the hood (axios, node-fetch, got, etc.)