Commit Graph

10 Commits

Author SHA1 Message Date
Alex Rudenko
e6265ee353
test: run new headless for the docker test (#10568) 2023-07-18 11:33:24 +02:00
Alex Rudenko
df4d60c187
feat!: switch to Chrome for Testing instead of Chromium (#10054)
Co-authored-by: Nikolay Vitkov <34244704+Lightning00Blade@users.noreply.github.com>
2023-05-02 08:53:40 +02:00
Nikolay Vitkov
c356e8f8f5
docs: use bash tag to get better formatting (#10086) 2023-04-26 11:32:33 +02:00
Alex Rudenko
3936600ba9
refactor: use @puppeteer/browsers for install (#9898)
Co-authored-by: Nikolay Vitkov <34244704+Lightning00Blade@users.noreply.github.com>
2023-03-28 09:27:50 +00:00
Tailgo
86441e313d
feat: use node18 as docker base image (#9456) 2023-01-02 11:00:16 +01:00
jrandolf
3df375baed
feat!: use ~/.cache/puppeteer for browser downloads (#9095) 2022-10-11 11:20:45 +00:00
jrandolf
f42336cf83
feat: separate puppeteer and puppeteer-core (#9023)
This PR moves the puppeteer source code into separate mono-repo packages:

- `puppeteer` and `puppeteer-core` are now separated into their own
packages.
- `puppeteer-core` has a new exports called `puppeteer-core/internal`
for internal usage.

Tests and various tools have been updated to accommodate the migration.
2022-10-05 14:17:03 +02:00
Seanghay Yath
34f8737218
feat: add Khmer (Cambodian) language support (#8809) 2022-08-18 08:57:00 +02:00
Alex Rudenko
eb6470931b
docs: add documentation about Docker (#8741)
Closes #3072
2022-08-05 11:00:09 +02:00
Alex Rudenko
936ed8607e feat: add Dockerfile (#8315)
This PR adds an official Dockerfile for Puppeteer. The content of the Dockerfile is practically the same as documented in troubleshooting.md:

1) It installs chrome-stable and dependencies via apt-get.
2) it installs a local Puppeteer build into the docker user's home folder.
3) configures required permissions for the user.
4) outputs licenses into the THIRD_PARTY_NOTICES file.

The local Puppeteer build is created by `docker/pack.sh` which is meant to be used in CI. This PR also includes a GitHub action that would build a docker image and run a smote test inside of it.

The next step would be actually publishing the docker image from GitHub Actions to GitHub Registry.
2022-08-02 13:18:47 +00:00