feat: Support remote-debugging-pipe and add loadExtension test/example #347
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Historically, the
--load-extensionoption 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-pipeis the official alternative. To support this,chrome-launcherneeds 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