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

@open-probe/proxy

v0.1.2

Published

Reverse proxy that injects open-probe runtime into any dev server.

Readme

@open-probe/proxy

Reverse proxy that injects @open-probe/core into any HTML response, so you can annotate elements on any dev server (Vite, Next, Nuxt, SvelteKit, plain Express…) without touching its build config.

Also bundles a minimal hand-rolled WebSocket annotation sink for the server (ws) transport, so you can pipe annotations to a file, stdout, or a custom editor integration without an extra service.

Install

pnpm add -D @open-probe/proxy

CLI

# Inject open-probe into any dev server
npx open-probe-proxy --target http://localhost:5173 --port 4000

# Plus a WebSocket sink that appends each annotation to a file
npx open-probe-proxy \
  --target http://localhost:5173 \
  --port 4000 \
  --ws --ws-output annotations.jsonl

| Flag | Default | Description | |------|---------|-------------| | --target <url> | (required) | Upstream dev server to proxy. | | --port <n> | 4000 | Port the proxy listens on. | | --host <h> | 127.0.0.1 | Bind address. | | --transport <t> | clipboard | clipboard / mcp / server. | | --mcp-endpoint <url> | http://127.0.0.1:3100 | MCP HTTP endpoint when --transport=mcp. | | --ws | off | Attach a WebSocket annotation sink at --ws-path. | | --ws-path <p> | /__open-probe/ws | WebSocket upgrade path. | | --ws-output <f> | stdout | File to append received annotation JSON. |

Programmatic API

import { createServer, attachWsSink } from '@open-probe/proxy';

const server = createServer({
  target: 'http://localhost:5173',
  port: 4000,
  injectScript: { transport: 'mcp', mcpEndpoint: 'http://127.0.0.1:3100' },
});
attachWsSink(server, { path: '/__open-probe/ws', onMessage: ann => save(ann) });

License

MIT