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

@refresh-dev/rce

v0.2.0

Published

**CLI tool for browser automation with time-travel debugging.**

Downloads

21

Readme

@refresh-dev/rce

CLI tool for browser automation with time-travel debugging.

RCE (Refresh Context Engine) provides a command-line interface for recording and controlling browser sessions with frame-by-frame DOM capture.

📦 Installation

npm install -g @refresh-dev/rce

🚀 Quick Start

# Start recording your app
rce dev --url http://localhost:3000 --serverCmd "npm run dev"

# Browser opens, RRWeb starts recording
# Navigate, click, interact - everything is captured

# In another terminal - control the browser
rce action browser_navigate --json '{"url":"http://localhost:3000/login"}'
rce action browser_type --json '{"selector":"#email","text":"[email protected]"}'
rce action browser_click --json '{"selector":"button[type=submit]"}'

# View captured frames
rce frames

# Time-travel screenshot
rce shot --index 50

# Generate DOM diff
rce diff --from 10 --to 50 --format html

📖 Commands

rce dev

Start browser recording session.

Options:

  • --url URL - Initial URL to navigate to
  • --serverCmd "cmd" - Dev server command to run
  • --headless - Run browser invisibly
  • --clear-state - Clear saved cookies/login
  • --port N - UI server port (default: 43210)

Example:

rce dev --url http://localhost:5173 --serverCmd "npm run dev"

rce action

Execute browser action on running session.

Available actions:

  • browser_navigate - Navigate to URL
  • browser_click - Click element (by CSS selector)
  • browser_type - Type into input
  • browser_press_key - Press keyboard key
  • browser_hover - Hover over element
  • browser_snapshot - Get HTML snapshot

Example:

rce action browser_click --json '{"selector":"#submit-btn"}'

rce frames

List all captured frames with timestamps.

rce frames --json

rce shot

Generate screenshot at specific frame.

rce shot --index 50              # Frame index
rce shot --at "+5000"            # 5 seconds from start
rce shot --at "2025-10-19T12:00" # Specific timestamp

rce diff

Generate DOM diff between two frames.

rce diff --from 10 --to 50 --format html
rce diff --from 10 --to 50 --format json

rce screenshot

Get latest screenshot.

rce screenshot --json

rce tabs

List browser tabs.

rce tabs list --json

🎯 Use with MCP

For Cursor integration, use the MCP server: @refresh-dev/rce-mcp

📁 Output Structure

.rce/
  ├── control.sock           # IPC socket for live control
  ├── storage-state.json     # Saved cookies/auth (persists login)
  └── data/<session-id>/
      ├── rrweb/
      │   ├── events.rrweb.jsonl  # DOM mutations
      │   └── frames.jsonl        # Frame index
      ├── screenshots/
      │   ├── latest.png          # Current screenshot
      │   └── shot_*.png          # Time-travel screenshots
      ├── logs/
      │   ├── console.jsonl       # Browser console
      │   ├── network.jsonl       # HTTP requests
      │   └── js_errors.jsonl     # JavaScript errors
      └── actions/
          └── actions.jsonl       # Action timeline

⚙️ Configuration File

Create rce.config.json in your project directory:

{
  "url": "http://localhost:3000",
  "serverCmd": "npm run dev",
  "bootWaitMs": 1500,
  "viewport": { "width": 1280, "height": 800 },
  "rrweb": {
    "recordCanvas": true,
    "collectFonts": true,
    "sampling": { "mousemove": 50, "input": "last" }
  },
  "ui": {
    "port": 43210,
    "screencastFps": 12,
    "jpegQuality": 70
  }
}

🔐 Session Persistence

RCE automatically saves browser state (cookies, localStorage) so login persists:

Login once:

rce dev --url http://localhost:3000
# Log in via browser UI
# Ctrl+C to stop

Next session - already logged in:

rce dev --url http://localhost:3000
# Opens with saved session ✓

Clear saved session:

rce dev --clear-state

🎥 UI Server

While rce dev runs, visit http://localhost:43210 to see:

  • Live browser feed
  • Real-time screenshot stream
  • Session metadata

🐛 Debugging

View logs:

tail -f .rce/data/<session-id>/logs/console.jsonl
tail -f .rce/data/<session-id>/logs/network.jsonl

Replay session:

rce serve  # Opens UI server for replay

📝 License

MIT