thunderstrike/puppeteer
thunderstrike/puppeteer
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
f04bec5a15
puppeteer/new-docs/puppeteer.puppeteer.connect.md
Jack Franklin 4846b8723c
chore(agnostification): split up launcher class (#6484) 
The `Launcher` class was serving two purposes:

1. Launch browsers
2. Connect to browsers

Number 1) only needs to be done in Node land, but 2) is agnostic; in a
browser version of Puppeteer we'll need the ability to connect over a
websocket to send commands back and forth.

As part of the agnostification work we needed to split the `Launcher` up
so that the connection part can be made agnostic. Additionally, I
removed dependencies on `https`, `http` and `URL` from Node, instead
leaning on fetch (via `node-fetch` if in Node land) and the browser
`URL` API (which was added to Node in Node 10).
2020-10-12 10:08:57 +01:00

1.0 KiB
Raw Blame History

Home > puppeteer > Puppeteer > connect

Puppeteer.connect() method

This method attaches Puppeteer to an existing browser instance.

Signature:

connect(options: BrowserOptions & {
        browserWSEndpoint?: string;
        browserURL?: string;
        transport?: ConnectionTransport;
        product?: Product;
    }): Promise<Browser>;

Parameters

Parameter Type Description
options BrowserOptions & { browserWSEndpoint?: string; browserURL?: string; transport?: ConnectionTransport; product?: Product; } Set of configurable options to set on the browser.

Returns:

Promise<Browser>

Promise which resolves to browser instance.

Remarks