Feature/config custom chrome executable path #3518
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue:
When running a custom install of Chrome, and not downloading Chromium (with the PUPPETEER_SKIP_CHROMIUM_DOWNLOAD, image snapshots are unable to start up. I ran across this issue when running Storyshots inside a Docker container already containing a Chrome installation.
What I did
Add a config parameter to use a Chrome executable path, instead of downloading Chromium inside of Puppeteer. If no parameter is selected, defaults to undefined and operates as normal.
How to test
Add a parameter and check if it references the correct Chrome. In my case:
/usr/local/bin/chrome