Skip to content

docs: update cypress/puppeteer docs to list limitations on Chrome branded browsers 137+ #31706

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 13, 2025
Merged

docs: update cypress/puppeteer docs to list limitations on Chrome branded browsers 137+ #31706

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions npm/puppeteer/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,9 +42,11 @@ Add the following in `tsconfig.json`:

## Compatibility

`@cypress/puppeteer` requires Cypress version 13.6.0 or greater.
Before using `@cypress/puppeteer`, ensure the following requirements are met:

Only Chromium-based browsers (e.g. Chrome, Chromium, Electron) are supported.
- Cypress 13.6.0+ is required.
- Only Chromium-based browsers are supported, such as Chrome for Testing, Chromium, and Electron.
- Chrome-branded browsers (e.g., standard Chrome) are not supported in version 137+ due to Chrome's removal of the `--load-extension` flag. We recommend using Chrome for Testing or Chromium instead. [See download instructions](https://www.chromium.org/getting-involved/download-chromium/).

## Usage

Expand Down Expand Up @@ -339,6 +341,7 @@ export default defineConfig({

If you receive this error in your command log, the Puppeteer plugin was unable to communicate with the Cypress extension. This extension is necessary in order to re-activate the main Cypress tab after a Puppeteer command, when running in open mode.

* If you're using a Chrome-branded browser (e.g., standard Chrome) in version 137+, you'll need to use Chrome for Testing or Chromium instead. [See download instructions](https://www.chromium.org/getting-involved/download-chromium/).
* Ensure this extension is enabled in the instance of Chrome that Cypress launches by visiting chrome://extensions/
* Ensure the Cypress extension is allowed by your company's security policy by its extension id, `caljajdfkjjjdehjdoimjkkakekklcck`

Expand Down
Loading