You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Lighthouse CLI requires the CHROME_PATH environment variable to be set to a Chrome/Chromium executable no older than Chrome stable. Based on the current situation, a developer seeking to use the Lighthouse feature must either:
use a base image that includes Chrome/Chromium.
write a custom Dockerfile that installs the Chrome/Chromium dependency.
I imagine there's utility in being able to quickly add a headless browser dependency that can be added as a feature layer through the devcontainers.json configuration, without requiring the developer to write a Dockerfile / select a different base image specifically for the Lighthouse testing tools.
There are other uses for a headless browser (eg., using with a tool like puppeteer).
Solution
I have forked the repository and have created this issue to help track my contribution. I am adding a chromium-apt-get feature and test suite.
The Lighthouse documentation describes how to set up a headless chromium installation here. Referencing this, once the chromium-apt-get feature is developed and tested, I will be creating a pull request to solve the issue.
The text was updated successfully, but these errors were encountered:
Requested Feature
chromium-apt-get
Add
chromium
feature to allow headless browser installation using theapt-get
package manager.Rationale
This project provides access to a Lighthouse CLI through its feature specification here:
ghcr.io/devcontainers-contrib/features/lighthouse-cli:1
.The Lighthouse CLI requires the
CHROME_PATH
environment variable to be set to a Chrome/Chromium executable no older than Chrome stable. Based on the current situation, a developer seeking to use the Lighthouse feature must either:I imagine there's utility in being able to quickly add a headless browser dependency that can be added as a feature layer through the
devcontainers.json
configuration, without requiring the developer to write a Dockerfile / select a different base image specifically for the Lighthouse testing tools.There are other uses for a headless browser (eg., using with a tool like
puppeteer
).Solution
I have forked the repository and have created this issue to help track my contribution. I am adding a
chromium-apt-get
feature and test suite.The Lighthouse documentation describes how to set up a headless chromium installation here. Referencing this, once the
chromium-apt-get
feature is developed and tested, I will be creating a pull request to solve the issue.The text was updated successfully, but these errors were encountered: