Changes between Version 1 and Version 2 of Ticket #52356, comment 6
- Timestamp:
- 12/03/2021 08:19:23 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #52356, comment 6
v1 v2 14 14 As a workaround you can set the `PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true` environment variable, which allows `npm install` to finish, but running tests won't work. Technically you should be able to install chromium independently (`brew install chromium`) and also set `PUPPETEER_EXECUTABLE_PATH`, but I haven't been able to get that working. 15 15 16 edit: actually, I do know the reason for the last thing . e2e tests are using `puppeteer-core` and that doesn't support the environment variables!16 edit: actually, I do know the reason for the last thing I mentioned. e2e tests are using `puppeteer-core` and that doesn't support the environment variables!