Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Puppeteer version out of sync with Chromium #247

Closed
robertbullen opened this issue Mar 26, 2024 · 0 comments · Fixed by #249
Closed

Puppeteer version out of sync with Chromium #247

robertbullen opened this issue Mar 26, 2024 · 0 comments · Fixed by #249
Labels

Comments

@robertbullen
Copy link

robertbullen commented Mar 26, 2024

Describe the bug

According to the README's How to use with Puppeteer section, this project follows Puppeteer's version mapping, but that doesn't appear to be the case.

To Reproduce

Execute the following:

docker run --rm -it zenika/alpine-chrome:with-puppeteer sh -c 'chromium --version && npm list puppeteer'

Note the output:

Chromium 122.0.6261.128 Alpine Linux
zenika-alpinechrome-withpuppeteer@1.0.0 /usr/src/app
`-- puppeteer@13.5.2

What is the expected behavior?

According to the version mapping, Puppeteer should be v22.5.0.

What is the actual behavior?

Puppeteer is v13.5.2.

Possible solution

Update the with-puppeteer subproject's dependencies to specify the correct Puppeteer version.

Logs

N/A.

Versions

Software Version(s) How-to
Chromium Chromium 122.0.6261.128 Alpine Linux docker container run -it --rm --entrypoint "" zenika/alpine-chrome chromium-browser --version
Image 8c88d61b7e7f627e44fdad3d4e681d71dc2fddcf22f2e3602a65622f76ffef44 docker image inspect --format='{{index .RepoDigests 0}}' zenika/alpine-chrome
Docker Engine 25.04 docker version

Additional context

Add any other context about the problem here.

zigarn added a commit that referenced this issue May 23, 2024
zigarn added a commit that referenced this issue May 30, 2024
zigarn added a commit that referenced this issue May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant