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.

Sign up for GitHub

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

Jump to bottom

docs(gatsby-plugin-preload-fonts): add external chrome env var #21845

Merged
merged 3 commits into from
Feb 29, 2020
Merged

docs(gatsby-plugin-preload-fonts): add external chrome env var #21845

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
cf92393
docs( gatsby-plugin-preload-fonts): hint to Puppeteer environment var…
nibtime Feb 28, 2020
4a2e952
fix typo
nibtime Feb 29, 2020
8f6b596
Update README.md
wardpeet Feb 29, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions packages/gatsby-plugin-preload-fonts/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,3 +137,6 @@ npm run preload-fonts -- --no-sandbox

This comes with [inherent security risks](https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md),
but you should be alright since you're only running it locally.

### Use different Chrome/Chromium executable
In some cases, you might have to point Puppeteer to an external installation of Chrome/Chromium (e.g., on Alpine Linux, the build-in version of Chromium does not work). You can set the `PUPPETEER_EXECUTABLE_PATH` environment variable to the path of your custom chromium installation. A list with all environment variables to configure Puppeteer can be found [at the official docs](https://pptr.dev/#?product=Puppeteer&version=v1.20.0&show=api-environment-variables).