Skip to content

Conversation

@Rob--W
Copy link
Contributor

@Rob--W Rob--W commented Apr 28, 2025

Historically, the --load-extension option in chromeFlags could be used to launch Chrome with an extension installed. This flag is no longer supported in official stable Chrome releases since Chrome 137. The --remote-debugging-pipe is the official alternative. To support this, chrome-launcher needs to pass two additional pipes.

This patch also includes a full test that serves as a form of documentation on how one can load an extension with chrome-launcher.

For more context, see mozilla/web-ext#3388

Fixes #289

Historically, the `--load-extension` option in chromeFlags could be used
to launch Chrome with an extension installed. This flag is no longer
supported in official stable Chrome releases since Chrome 137. The
`--remote-debugging-pipe` is the official alternative. To support this,
`chrome-launcher` needs to pass two additional pipes.

This patch also includes a full test that serves as a form of
documentation on how one can load an extension with `chrome-launcher`.

For more context, see mozilla/web-ext#3388

Fixes GoogleChrome#289
Copy link
Member

@paulirish paulirish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Man, what a dream of a PR.
I have no notes. It's great.

Big thank you!

@paulirish paulirish merged commit 9817a05 into GoogleChrome:main May 6, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

crash when launch with remote debugging pipe

2 participants