CodeVetter · Repo Unpack · Contributor handoff
puppeteer/puppeteer
Tests and CI were inspected, not executed; this handoff is a source-based starting point with bounded coverage. Begin in the owning package and trace the public abstraction through its protocol or Node implementation before editing. Preserve browser-runtime compatibility, asynchronous cleanup, generated documentation conventions, and expectation semantics. Future verification commands require an execution-authorized task and the repository verification skill.
- Read package.json and the owning manifest first: root test/build scripts delegate through Wireit, and workspace builds include dependency builds rather than only the named package.
- Launch changes should be reviewed across PuppeteerNode, ChromeLauncher, and BrowserLauncher; temporary profiles are cleaned separately from caller-owned Chrome profiles.
- Public API edits require TSDoc with @public/@internal tags; docs/api Markdown is generated and should not be edited manually, and CI checks regenerated-document differences.
- Preserve strict TypeScript checks and established formatting: noImplicitOverride/noUncheckedIndexedAccess are enabled; Prettier uses single quotes, no bracket spaces, trailing commas, and unparenthesized single arrow parameters.
- Before future execution, read puppeteer-verification: it prescribes temporary .only markers for focused Chrome/Firefox tests, npm run unit for units, and npm run build; its npm run format recommendation performs automatic mutations.
- Tests and CI in this investigation were only inspected: suite definitions and expected FAIL/SKIP entries must be considered before treating a future runner success as feature coverage.
- Do not assume CDP/BiDi parity: Firefox defaults to BiDi, Chrome defaults to CDP, and URL allowlist/blocklist configuration is explicitly rejected for BiDi.
- Installation edits need coordinated review of provider fallback, custom executable metadata, incomplete-install detection, extraction backends, and optional peer dependencies; browser-package tests themselves include a download script.