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

@boomarche/beacon

v0.1.1

Published

Scripted feature-showcase animations: drive a web app with Playwright, render polished MP4s with Remotion.

Readme

Beacon

Scripted feature-showcase animations. Drive a web app with Playwright, render polished MP4s with Remotion. Re-renders cleanly when your UI changes — your scripts are source code, not screen recordings.

┌──────────────────┐    ┌──────────────────┐    ┌──────────────────┐
│  showcase.ts     │───▶│  Playwright      │───▶│  Remotion        │
│  (your script)   │    │  drives the app  │    │  composites the  │
│                  │    │  + captures      │    │  polished MP4    │
└──────────────────┘    └──────────────────┘    └──────────────────┘

Install

npm install -g @boomarche/beacon
beacon --help

First run also fetches Chromium (~150 MB, one time).

Quick start

Record a session, then render it

beacon record https://your-app.example.com --callouts -o demo.ts
beacon render demo.ts -o demo.mp4

beacon record opens a real Chromium window with Playwright's Inspector attached. Click through the demo you want, close the browser, and Beacon writes a demo.ts file with auto-disambiguated selectors and (optionally) callouts you chose interactively.

Write a script by hand

// demo.ts
import { showcase } from "@boomarche/beacon"

export default showcase(
  "My feature demo",
  { target: "https://your-app.example.com", viewport: { w: 1440, h: 900 } },
  async (s) => {
    await s.callout("Start by clicking 'New'", { duration: 1500 })
    await s.click('[data-testid="new-project"]')
    await s.type("Q3 Roadmap")
    await s.click("button:has-text('Create')")
    await s.callout("Done!", { duration: 2500 })
    await s.caption("Built with Beacon")
  },
)

Then:

beacon render demo.ts -o demo.mp4

DSL reference

The showcase() factory takes a title, options (target URL + viewport), and an async (s) => { ... } body. Inside the body:

| Verb | Effect | | --- | --- | | await s.navigate(url) | Cross-fade to a new URL | | await s.click(selector) | Cursor eases to target, click ripple, auto-zoom | | await s.type(text, { perCharMs? }) | Realistic per-character typing | | await s.hover(selector) | Cursor eases to target with hover-state | | await s.wait(ms) | Hold for ms milliseconds | | await s.callout(text, { target?, side?, duration? }) | Pill tooltip with dim BG, optionally anchored to a selector | | await s.zoom({ selector?, factor? }) | Zoom into a region (or viewport-centre if no selector) | | await s.caption(text, { duration? }) | Lower-third caption bar |

Selectors accept any Playwright locator string: plain CSS (#submit), role selectors (role=button[name="Save"]), text matchers (text=Click here), and chained filters (role=link[name="X"] >> nth=0).

CLI

beacon record <url>      Record a browser session → emit a showcase script
  -o, --out <file>          output .ts script path (default: showcase.ts)
  --title <title>           showcase title (defaults to hostname)
  --no-auto-wait            skip auto-detected pauses between actions
  --callouts                pick actions to annotate via TUI

beacon render <script>   Render a showcase script to MP4
  -o, --out <file>          output MP4 path (default: showcase.mp4)
  --fps <n>                 frames per second (default: 30)
  --width <n>               viewport width
  --height <n>              viewport height

beacon preview <script>  Open Remotion Studio for live preview

beacon init <dir>        Scaffold a new showcase project
  --name <name>             package name

Architecture

Three independently testable layers communicating through a versioned CaptureBufferSnapshot:

  1. @beacon/core — script API and types
  2. @beacon/driver-playwright — Playwright backend, executes operations, captures frames + semantic events
  3. @beacon/render — Remotion compositions (synthetic cursor, click ripple, callouts, zoom)

This boundary is what lets the renderer stay decoupled from the capture mechanism — a future Tauri-app driver (@beacon/driver-tauri) or a marker-assisted recorder will share the same renderer.

Roadmap

  • v1 (current): web targets via Playwright, MP4 output, recorder, opinionated renderer.
  • v1.1: Tauri-app driver (WebDriver-protocol-based, shares most code with the Playwright driver).
  • v2: integration with capture SDKs so Beacon can render videos from in-app event streams emitted by your own apps.

Status

v1. Used in production for Boomarche showcases; cross-platform CI on macOS / Windows / Linux. Issues and PRs welcome at github.com/boomarche/beacon.

License

MIT © Kaan Dinler