Allow using remote Chrome with puppeteer

Puppeteer allows connecting to chrome via a web socket or URL.

See: Puppeteer docs

This would disallow using args (they’d have to be added on the browser-side), though.

Proposal: Add a remoteOptions key to engineOptions (or maybe a separate remote: bool flag, too?); when this is filled, use await puppeteer.connect() instead of puppeteer.launch().

Use cases:

• It would be beneficial mainly for dockerized environments, as it would be more in-line with the docker way (one process per container).

[garris]

This is cool – thank you! I have some changes on the npm canary branch that need to be released. I will try to get those out next week, then we can merge these and put it out on the canary branch. More later. Cheers!

[danielepolencic]

I’m interested in this as well. I’d like to leverage a service such as browserless.io instead of maintaining my own puppeteer locally. Happy to help with rebasing/amending the PR if it can be merged.