4846b8723c
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).
29 lines
854 B
Markdown
29 lines
854 B
Markdown
<!-- Do not edit this file. It is automatically generated by API Documenter. -->
|
|
|
|
[Home](./index.md) > [puppeteer](./puppeteer.md) > [ProductLauncher](./puppeteer.productlauncher.md)
|
|
|
|
## ProductLauncher interface
|
|
|
|
Describes a launcher - a class that is able to create and launch a browser instance.
|
|
|
|
<b>Signature:</b>
|
|
|
|
```typescript
|
|
export interface ProductLauncher
|
|
```
|
|
|
|
## Properties
|
|
|
|
| Property | Type | Description |
|
|
| --- | --- | --- |
|
|
| [executablePath](./puppeteer.productlauncher.executablepath.md) | () => string | |
|
|
| [product](./puppeteer.productlauncher.product.md) | [Product](./puppeteer.product.md) | |
|
|
|
|
## Methods
|
|
|
|
| Method | Description |
|
|
| --- | --- |
|
|
| [defaultArgs(object)](./puppeteer.productlauncher.defaultargs.md) | |
|
|
| [launch(object)](./puppeteer.productlauncher.launch.md) | |
|
|
|