puppeteer/utils
Andrey Lushnikov 13e8580a34 Use puppeteer.launch instead of browser constructor (#255)
This patch:
- split browser launching logic from Browser into `lib/Launcher.js`
- introduce `puppeteer` namespace which currently has a single `launch`
  method to start a browser

With this patch, the browser is no longer created with the `new
Browser(..)` command. Instead, it should be "launched" via the
`puppeteer.launch` method:

```js
const puppeteer = require('puppeteer');
puppeteer.launch().then(async browser => {
  ...
});
```

With this approach browser instance lifetime matches the lifetime of
actual browser process. This helps us:
- remove proxy streams, e.g. browser.stderr and browser.stdout
- cleanup browser class and make it possible to connect to remote
  browser
- introduce events on the browser instance, e.g. 'page' event. In case
  of lazy-launching browser, we should've launch browser when an event
  listener is added, which is unneded comlpexity.
2017-08-14 18:08:06 -07:00
..
doclint Use puppeteer.launch instead of browser constructor (#255) 2017-08-14 18:08:06 -07:00
check_availability.js Use const a lot fo places (#188) 2017-08-02 12:06:47 -07:00
ChromiumDownloader.js Use const a lot fo places (#188) 2017-08-02 12:06:47 -07:00
fetch_devices.js Convert DevicesDescriptors into puppeteer format 2017-07-20 17:49:15 -07:00