Skip to content
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

Adding possibility to use external chrome #410

Merged
merged 4 commits into from Nov 8, 2018

Conversation

axelssonHakan
Copy link
Member

No description provided.

Copy link
Contributor

@stoffeastrom stoffeastrom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should move this under chrome so we are consistent. Since the https://github.com/GoogleChrome/puppeteer/blob/v1.10.0/docs/api.md#puppeteerconnectoptions
has more options you might want to pass them also.
Add a launch flag instead that is true default
So if you pass --no-launch it will connect instead and pass the this.argv.chrome

@coveralls
Copy link

coveralls commented Nov 7, 2018

Coverage Status

Coverage decreased (-0.1%) to 38.421% when pulling ca8db3f on puppeteer_browserWSEndpoint into e3a184d on master.

@axelssonHakan
Copy link
Member Author

Updated after review - thanks @stoffeastrom

@axelssonHakan axelssonHakan merged commit 3de0d48 into master Nov 8, 2018
@axelssonHakan axelssonHakan deleted the puppeteer_browserWSEndpoint branch November 8, 2018 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants