-
Notifications
You must be signed in to change notification settings - Fork 607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow using remote Chrome with puppeteer #1002
Comments
3 things...
|
Disclaimer: this is just headcanon, an actual implementation might be more difficult. :) |
Thinking of it, another use case would be scalability (e.g in CI/CD when having lots of tests). Backstop on its own doesn't really use a lot of resources, the main hogs are the browsers. Having the ability to move the resource-intensive stuff to a different machine should help with this. |
Wow. That just made my head explode. 🤯
|
Very cool idea. Would be fantastic if someone wants to build it. |
Created a PR for it (note, I'm mhavelant, this is only my personal account, the other one is my work account). :) |
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! |
@garris is this still going to be merged? |
I'm interested in this as well. |
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 toengineOptions
(or maybe a separateremote: bool
flag, too?); when this is filled, useawait puppeteer.connect()
instead ofpuppeteer.launch()
.Use cases:
The text was updated successfully, but these errors were encountered: