@elysiumoss/ui-capture - v0.3.0
    Preparing search index...

    Interface CaptureVideoConfig

    interface CaptureVideoConfig {
        waitTime: number;
        ffmpegPath: string;
        videoOptions: { duration: number; interactions: boolean };
        colorScheme: "light" | "dark" | "no-preference";
        startUrl: string;
        prepare?: (page: Page) => Effect<void, CaptureError>;
    }
    Index
    waitTime: number
    ffmpegPath: string
    videoOptions: { duration: number; interactions: boolean }
    colorScheme: "light" | "dark" | "no-preference"

    Must match the screenshot context, or a run's stills and video disagree.

    startUrl: string

    Where the capture began — the URL the recording context navigates to before prepare replays the script.

    Deliberately supplied by the caller rather than read off the page being captured: by the time video runs, a scripted state has already driven that page, so its current URL is where the script ended. Replaying the script from there records the wrong thing — a step that navigates would run from the wrong entry point, and a first step that assumes the entry view fails outright.

    prepare?: (page: Page) => Effect<void, CaptureError>

    Replays a scripted state inside the recording context.

    Without it the video context would navigate and record the unscripted boot view while the stills show the scripted state — the two silently disagreeing. Undefined for route captures, so existing behaviour is untouched.