https://github.com/heroku/heroku-buildpack-google-chrome

Run (headless) Google Chrome on Heroku
https://github.com/heroku/heroku-buildpack-google-chrome

google-chrome heroku-buildpack

Last synced: about 1 month ago
JSON representation

Run (headless) Google Chrome on Heroku

• Host: GitHub
• URL: https://github.com/heroku/heroku-buildpack-google-chrome
• Owner: heroku
• Created: 2017-01-20T11:36:24.000Z (almost 8 years ago)
• Default Branch: master
• Last Pushed: 2024-07-24T14:30:06.000Z (4 months ago)
• Last Synced: 2024-09-30T17:02:15.417Z (about 1 month ago)
• Topics: google-chrome, heroku-buildpack
• Language: Shell
• Homepage:
• Size: 71.3 KB
• Stars: 297
• Watchers: 81
• Forks: 364
• Open Issues: 44
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • Support: support/test.sh

Awesome Lists containing this project

README

        
## WARNING: `heroku-buildpack-google-chrome` is deprecated

This buildpack is deprecated and is no longer being maintained. Use (https://github.com/heroku/heroku-buildpack-chrome-for-testing.

# heroku-buildpack-google-chrome

This buildpack downloads and installs (headless) Google Chrome from your choice

of release channels.

> [!IMPORTANT]

> When used with Chromedriver, the Chromedriver version (installed by a different buildpack) falls out of sync with Chrome causing build failures.

> 

> **Instead, please use [Chrome for Testing buildpack](https://github.com/heroku/heroku-buildpack-chrome-for-testing)**, which installs  [matching Chrome + Chromedriver versions](https://googlechromelabs.github.io/chrome-for-testing/).

## Channels

You can choose your release channel by specifying `GOOGLE_CHROME_CHANNEL` as

a config var for your app, in your app.json (for Heroku CI and Review Apps),

or in your pipeline settings (for Heroku CI).

Valid values are `stable`, `beta`, and `unstable`. If unspecified, the `stable`

channel will be used.

## Shims and Command Line Flags

This buildpack installs shims that always add `--headless`, `--disable-gpu`, 

`--no-sandbox`, and `--remote-debugging-port=9222` to any `google-chrome` 

command as you'll have trouble running Chrome on a Heroku dyno otherwise.

You'll have two of these shims on your path: `google-chrome` and

`google-chrome-$GOOGLE_CHROME_CHANNEL`. They both point to the binary of

the selected channel.

## Selenium

> [!CAUTION]

> To use Selenium, do not install this buildpack.

>

> **Instead, please use [Chrome for Testing buildpack](https://github.com/heroku/heroku-buildpack-chrome-for-testing)**, which installs  [matching Chrome + Chromedriver versions](https://googlechromelabs.github.io/chrome-for-testing/).

## Releasing a new version

Make sure you publish this buildpack in the buildpack registry

`heroku buildpacks:publish heroku/google-chrome master`