Puppeteer v22 Headless Mode Transition Decision

Puppeteer v22 Headless Mode Transition

With the release of Puppeteer 22, the default headless configuration switched from the legacy chrome-headless-shell binary to the full Chrome headless implementation. This change introduces differences in rendering fidelity, extension support, GPU/WebGL availability, and anti‑bot detection behavior.

Constraints and Decision Points

Teams evaluating a migration must consider the trade‑off between the lightweight shell binary—beneficial for CI pipelines and low‑resource environments—and the comprehensive feature set of the new headless mode, which may be required for pages that rely on extensions, advanced CSS, or GPU acceleration. Additionally, the binary size, Docker image footprint, and the need to pin specific Chromium versions can influence the choice.

Unresolved Questions

Which rendering discrepancies (e.g., font rasterization or PDF output) are most critical for our use case when switching from shell to the new headless mode? How does the new headless implementation impact page‑load latency and resource consumption compared to the legacy shell? Are there specific anti‑bot detection thresholds that differ between the two headless binaries, potentially affecting test stability?