Skip to content

Update load extension + puppeteer docs #6182

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.

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

Closed
6 tasks
jennifer-shehane opened this issue May 13, 2025 · 4 comments · Fixed by #6183
Closed
6 tasks

Update load extension + puppeteer docs #6182

jennifer-shehane opened this issue May 13, 2025 · 4 comments · Fixed by #6183
Assignees

Comments

@jennifer-shehane
Copy link
Member

Description

In Chrome 137, Chrome is removing the --load-extension flag from branded builds of Chrome.

URL of Issue(s)

https://docs.cypress.io/api/node-events/browser-launch-api#Add-browser-extensions

Steps to replicate

We'll want to update the docs to suggest users use Chrome for Testing or Chromium browsers to load extensions.

Browser

No response

Device

  • PC
  • Mac
  • iPhone
  • iPad
  • Android Phone
  • Android Tablet

Additional Information

No response

@alexsch01
Copy link
Contributor

As I said in a different message, Cypress by default includes this flag

@MikeMcC399
Copy link
Contributor

@jennifer-shehane

Cypress Docker image examples may help here:

@jennifer-shehane
Copy link
Member Author

@MikeMcC399 Hmm, yah I wonder if we should point to these docs instead of Chromes

@MikeMcC399
Copy link
Contributor

@jennifer-shehane

Hmm, yah I wonder if we should point to these docs instead of Chromes

I see you've added links to the Cypress docs. 👍🏻

The Chrome / Chromium documentation like https://www.chromium.org/getting-involved/download-chromium/ is not the most user-friendly, and it's partially out of date.

The Cypress Docker example READMEs give easy to follow steps. They are oriented to Debian, so don't cover other OS, like Ubuntu, Windows or macOS. Hopefully they will be of use to at least some users!

I guess we'll see in a couple of weeks, when Chrome 137 is released as stable!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants