We recently updated our app from @percy/agent to use the CLI package. The docs for skipping downloading Chromium appear to no longer accurate (or are solely for the agent package).
I tried searching for PUPPETEER_SKIP_CHROMIUM_DOWNLOAD and PUPPETEER_EXECUTABLE_PATH in this repo and it looks like they recently disappeared in the last two weeks. The CLI fails to find our previously installed browser because (I think?) the code assumes a fixed location for the pre-existing Chrome/Chromium executable.
This is a blocker for us to update because in addition to the extra bulk of downloading Chromium, the automated download doesn't work on Alpine Linux.
I think this probably works if I can symlink our existing executable (currently installed at /usr/bin/chromium-browser) to the location that the package expects. Would that be enough? Where would we point it the symlink to work around this?
Thanks for your help.
We recently updated our app from
@percy/agentto use the CLI package. The docs for skipping downloading Chromium appear to no longer accurate (or are solely for the agent package).I tried searching for
PUPPETEER_SKIP_CHROMIUM_DOWNLOADandPUPPETEER_EXECUTABLE_PATHin this repo and it looks like they recently disappeared in the last two weeks. The CLI fails to find our previously installed browser because (I think?) the code assumes a fixed location for the pre-existing Chrome/Chromium executable.This is a blocker for us to update because in addition to the extra bulk of downloading Chromium, the automated download doesn't work on Alpine Linux.
I think this probably works if I can symlink our existing executable (currently installed at
/usr/bin/chromium-browser) to the location that the package expects. Would that be enough? Where would we point it the symlink to work around this?Thanks for your help.