the package export surface in src/index.ts
the captureBrowserRoots() programmatic API
the capture CLI entry in src/cli/capture.ts
Vite dev-server startup for scene packages
Playwright-driven export of each data-scenario-capture-root element as its own PNG

Usage

pnpm -F @proj-airi/vishot-runner-browser capture -- ../scenarios-stage-tamagotchi-browser --output-dir ../scenarios-stage-tamagotchi-browser/artifacts/final
pnpm -F @proj-airi/scenarios-stage-tamagotchi-browser capture

The browser capture package can run directly against a scene package root, or indirectly through the consumer package's own capture script. In both cases it starts the scene package's Vite app, opens it in Chromium, waits for the frontend ready signal, and exports each capture root into packages/scenarios-stage-tamagotchi-browser/artifacts/final.

Programmatic usage from a scene package looks like this:

import path from 'node:path'

import { captureBrowserRoots } from '@proj-airi/vishot-runner-browser'

const sceneAppRoot = path.resolve(process.cwd())

await captureBrowserRoots({
  sceneAppRoot,
  routePath: '/',
  outputDir: path.resolve(sceneAppRoot, 'artifacts', 'final'),
})

Notes

captureBrowserRoots() accepts either sceneAppRoot or baseUrl.
Scene packages mark readiness through window.__SCENARIO_CAPTURE_READY__.
The CLI treats <render-entry> as the scene package root and captures the default / route.
The parser accepts repeated --root flags for named capture roots.