Puppeteer browser launch configuration for Chromium version mismatches

Puppeteer manages the browser lifecycle via the puppeteer.launch() method, which by default relies on a bundled Chromium binary compatible with the installed library version. In environments where the system-installed browser is updated independently of the Puppeteer package, a version mismatch can prevent the browser from initializing.

While the executablePath option allows pointing to a specific binary, there is uncertainty regarding the most reliable way to programmatically detect a version incompatibility before the launch process fails. Ensuring the library version aligns with the binary version is critical for maintaining stability in automated CI/CD pipelines.

• What is the recommended approach to verify binary compatibility before calling puppeteer.launch()?
• Are there configuration flags that allow Puppeteer to attempt a fallback to a different binary version if the primary path fails?