931d4fced5
🤖 I have created a release *beep* *boop* --- <details><summary>puppeteer: 19.4.0</summary> ## [19.4.0](https://github.com/puppeteer/puppeteer/compare/puppeteer-v19.3.0...puppeteer-v19.4.0) (2022-12-07) ### Features * **chromium:** roll to Chromium 109.0.5412.0 (r1069273) ([#9364](https://github.com/puppeteer/puppeteer/issues/9364)) ([1875da6](1875da6191)), closes [#9233](https://github.com/puppeteer/puppeteer/issues/9233) ### Dependencies * The following workspace dependencies were updated * dependencies * puppeteer-core bumped from 19.3.0 to 19.4.0 </details> <details><summary>puppeteer-core: 19.4.0</summary> ## [19.4.0](https://github.com/puppeteer/puppeteer/compare/puppeteer-core-v19.3.0...puppeteer-core-v19.4.0) (2022-12-07) ### Features * ability to send headers via ws connection to browser in node.js environment ([#9314](https://github.com/puppeteer/puppeteer/issues/9314)) ([937fffa](937fffaedc)), closes [#7218](https://github.com/puppeteer/puppeteer/issues/7218) * **chromium:** roll to Chromium 109.0.5412.0 (r1069273) ([#9364](https://github.com/puppeteer/puppeteer/issues/9364)) ([1875da6](1875da6191)), closes [#9233](https://github.com/puppeteer/puppeteer/issues/9233) * **puppeteer-core:** keydown supports commands ([#9357](https://github.com/puppeteer/puppeteer/issues/9357)) ([b7ebc5d](b7ebc5d9bb)) ### Bug Fixes * **puppeteer-core:** avoid type instantiation errors ([#9370](https://github.com/puppeteer/puppeteer/issues/9370)) ([17f31a9](17f31a9ee4)), closes [#9369](https://github.com/puppeteer/puppeteer/issues/9369) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
49 lines
1.2 KiB
Markdown
49 lines
1.2 KiB
Markdown
# Chrome Extensions
|
|
|
|
Puppeteer can be used for testing Chrome Extensions.
|
|
|
|
:::caution
|
|
|
|
Extensions in Chrome/Chromium currently only work in non-headless mode and
|
|
experimental Chrome headless mode.
|
|
|
|
:::
|
|
|
|
The following is code for getting a handle to the
|
|
[background page](https://developer.chrome.com/extensions/background_pages) of
|
|
an extension whose source is located in `./my-extension`:
|
|
|
|
```ts
|
|
const puppeteer = require('puppeteer');
|
|
|
|
(async () => {
|
|
const pathToExtension = require('path').join(__dirname, 'my-extension');
|
|
const browser = await puppeteer.launch({
|
|
headless: 'chrome',
|
|
args: [
|
|
`--disable-extensions-except=${pathToExtension}`,
|
|
`--load-extension=${pathToExtension}`,
|
|
],
|
|
});
|
|
const backgroundPageTarget = await browser.waitForTarget(
|
|
target => target.type() === 'background_page'
|
|
);
|
|
const backgroundPage = await backgroundPageTarget.page();
|
|
// Test the background page as you would any other page.
|
|
await browser.close();
|
|
})();
|
|
```
|
|
|
|
:::note
|
|
|
|
Chrome Manifest V3 extensions have a background ServiceWorker of type
|
|
'service_worker', instead of a page of type 'background_page'.
|
|
|
|
:::
|
|
|
|
:::note
|
|
|
|
It is not yet possible to test extension popups or content scripts.
|
|
|
|
:::
|