From cf923930f452ce476ac2867acfe3c26f2a5ccf14 Mon Sep 17 00:00:00 2001 From: nibtime <52962482+nibtime@users.noreply.github.com> Date: Fri, 28 Feb 2020 22:18:06 +0100 Subject: [PATCH 1/3] docs( gatsby-plugin-preload-fonts): hint to Puppeteer environment variables --- packages/gatsby-plugin-preload-fonts/README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/packages/gatsby-plugin-preload-fonts/README.md b/packages/gatsby-plugin-preload-fonts/README.md index c04f04be9396d..9e4821f7bcb36 100644 --- a/packages/gatsby-plugin-preload-fonts/README.md +++ b/packages/gatsby-plugin-preload-fonts/README.md @@ -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. + +#### Environment Variables +In some cases you might have to point Puppeteer to an external installation of Chromium (e.g. on Alpine Linux, the build-in version of Chromium does not work). To do that, you can set the `PUPPETEER_EXECUTABLE_PATH` environment variable. A list with all enviroment variables to configure Puppeteer can be found [here](https://pptr.dev/#?product=Puppeteer&version=v1.20.0&show=api-environment-variables). From 4a2e952c48fa4b9ad98871a8a6f3fa61702f7f68 Mon Sep 17 00:00:00 2001 From: nibtime <52962482+nibtime@users.noreply.github.com> Date: Sat, 29 Feb 2020 02:34:25 +0100 Subject: [PATCH 2/3] fix typo --- packages/gatsby-plugin-preload-fonts/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/gatsby-plugin-preload-fonts/README.md b/packages/gatsby-plugin-preload-fonts/README.md index 9e4821f7bcb36..372cc93f35b9d 100644 --- a/packages/gatsby-plugin-preload-fonts/README.md +++ b/packages/gatsby-plugin-preload-fonts/README.md @@ -139,4 +139,4 @@ This comes with [inherent security risks](https://chromium.googlesource.com/chro but you should be alright since you're only running it locally. #### Environment Variables -In some cases you might have to point Puppeteer to an external installation of Chromium (e.g. on Alpine Linux, the build-in version of Chromium does not work). To do that, you can set the `PUPPETEER_EXECUTABLE_PATH` environment variable. A list with all enviroment variables to configure Puppeteer can be found [here](https://pptr.dev/#?product=Puppeteer&version=v1.20.0&show=api-environment-variables). +In some cases you might have to point Puppeteer to an external installation of Chromium (e.g. on Alpine Linux, the build-in version of Chromium does not work). To do that, you can set the `PUPPETEER_EXECUTABLE_PATH` environment variable. A list with all environment variables to configure Puppeteer can be found [here](https://pptr.dev/#?product=Puppeteer&version=v1.20.0&show=api-environment-variables). From 8f6b5968596b3811fab5cb3436a76858621deb00 Mon Sep 17 00:00:00 2001 From: Ward Peeters <ward@coding-tech.com> Date: Sat, 29 Feb 2020 12:46:05 +0100 Subject: [PATCH 3/3] Update README.md --- packages/gatsby-plugin-preload-fonts/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/gatsby-plugin-preload-fonts/README.md b/packages/gatsby-plugin-preload-fonts/README.md index 372cc93f35b9d..36a440caa2c11 100644 --- a/packages/gatsby-plugin-preload-fonts/README.md +++ b/packages/gatsby-plugin-preload-fonts/README.md @@ -138,5 +138,5 @@ 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. -#### Environment Variables -In some cases you might have to point Puppeteer to an external installation of Chromium (e.g. on Alpine Linux, the build-in version of Chromium does not work). To do that, you can set the `PUPPETEER_EXECUTABLE_PATH` environment variable. A list with all environment variables to configure Puppeteer can be found [here](https://pptr.dev/#?product=Puppeteer&version=v1.20.0&show=api-environment-variables). +### 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).