This repository has been archived by the owner on Nov 24, 2018. It is now read-only.
Enable chromeFlags and customize userDataDir #310
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- fixes schickling#146 pdf only works in headless mode - fixes schickling#184 Add chromePath and chromeFlags to ChromelessOptions
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes #192 which added the chromeFlags option but wasn't functional because of a misuse of the JS spread operator (user's custom settings were automatically ignored).
Also, it adds a new option userDataDir, which is the user profile's path. Useful if you want to keep separate user profiles.
Apart from the many possibilities chromeFlags provides, there's the ability to set a proxy programatically:
chromeFlags: ['--proxy-server=127.0.0.1:8082']