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

siterpc

v0.1.4

Published

CLI-first SiteRPC runtime for exposing Playwright-controlled pages as callable tools

Readme

SiteRPC

CLI-first SiteRPC runtime for exposing Playwright-controlled pages as callable tools.

Install

Install the full runtime on the worker machine:

npm install siterpc

Install the lightweight remote client on machines that only call an existing worker:

npm install siterpc-client

Quick Start

Create a generic starter project:

npx siterpc init my-site
cd my-site

Download the example project from a GitHub repository:

npx siterpc example your-org/site-rpc

Copy that repository's templates/example/ into a local directory:

npx siterpc example your-org/site-rpc ./my-example

Help

siterpc --help
siterpc help call
siterpc help example

Config Discovery

Local runtime commands automatically look for a config file from the current directory upward in this order:

  1. siterpc.config.ts
  2. siterpc.config.mjs
  3. siterpc.config.js

You can still override discovery explicitly:

siterpc call --config ./siterpc.config.ts --tool app_search --input '{"keyword":"hello"}'

--remote ws://... always bypasses local discovery.

Runtime Commands

Call a tool with local config discovery:

siterpc call --tool app_someTool --input '{"key":"value"}'

Inspect worker state:

siterpc status

Close one site page:

siterpc close-page --accountId default --siteName app

Stop the local worker:

siterpc stop

Run a foreground worker explicitly:

siterpc worker --config ./siterpc.config.ts --listen-host 127.0.0.1 --listen-port 42100

Call a remote worker:

siterpc call --remote ws://127.0.0.1:42100 --tool app_someTool --input '{"key":"value"}'

Use the lightweight client when the caller does not need local browser control:

siterpc-client call --remote ws://127.0.0.1:42100 --tool app_someTool --input '{"key":"value"}'
siterpc-client status --remote ws://127.0.0.1:42100

Config Shape

import { defineConfig } from "siterpc";
import appSite from "./sites/app.js";

export default defineConfig({
  browser: {
    channel: "chrome",
    headless: false,
    defaultTimeout: 30_000,
    args: ["--disable-blink-features=AutomationControlled"]
  },
  resources: {
    root: "./resources"
  },
  accounts: [
    {
      id: "default",
      userDataDir: "./.siterpc-browser-data/default",
      sites: ["app"]
    }
  ],
  sites: [appSite]
});

Declarative Sites

import { defineSite } from "siterpc";

export default defineSite({
  name: "app",
  displayName: "App Site",
  globalIntercepts: [],
  pages: {
    main: {
      url: "https://example.com/",
      intercepts: []
    }
  },
  tools: []
});

For a complete real-world reference, use siterpc example <owner/repo>.