From 00909c825855698e4caad4e19b2b18b94fe6e372 Mon Sep 17 00:00:00 2001 From: Vance Ingalls Date: Sun, 22 Mar 2026 01:31:33 -0700 Subject: [PATCH] fix: revert parity harness to puppeteer-core with channel: chrome The puppeteer import caused protocol timeout issues. Revert to puppeteer-core but add channel: "chrome" to auto-discover the Chrome binary installed by 'puppeteer browsers install'. Co-Authored-By: Claude Opus 4.6 (1M context) --- packages/producer/src/parity-harness.ts | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/packages/producer/src/parity-harness.ts b/packages/producer/src/parity-harness.ts index b3a1631a7..917e48e6b 100644 --- a/packages/producer/src/parity-harness.ts +++ b/packages/producer/src/parity-harness.ts @@ -3,7 +3,7 @@ import { existsSync, mkdirSync, writeFileSync } from "node:fs"; import { dirname, join, resolve } from "node:path"; import process from "node:process"; import { spawnSync } from "node:child_process"; -import puppeteer, { type Page } from "puppeteer"; +import puppeteer, { type Page } from "puppeteer-core"; import { MEDIA_VISUAL_STYLE_PROPERTIES, quantizeTimeToFrame } from "./utils/parityContract.js"; type ParityHarnessOptions = { @@ -270,6 +270,7 @@ async function run(): Promise { ensureDir(options.artifactsDir); const browser = await puppeteer.launch({ + channel: "chrome", headless: true, defaultViewport: { width: options.width,