-
-
Notifications
You must be signed in to change notification settings - Fork 124
V4.0.0 get Error: Could not find Chrome (ver. 119.0.6045.105) #218
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
Comments
Same issue🥲 no updates? |
Did you check the troubleshooting section of Puppeteer documentation https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md? Since, I updated Puppeteer you might do some changes on your part. That is why I made a major version to warn about the fact it might contains breaking changes on puppeteer side. |
The same things happened to me, In my case node-html-to-image was used in node server, ever thing is ok by locally run but not in deploying, I don't know what's going on. `Could not find Chrome (ver. 128.0.6613.119). This can occur if either
package detail & use case |
same issues |
any resolutions? Looking to resolve myself. |
I have been using node-html-to-image for two years and it worked well. Recently I updated all dependencies including this package to v4.0.0 and it doesn't work any more.
Call
nodeHtmlToImage()
it just thrown an error:I googled every error message, read many pages in GIthub and Stack Overflow and tried different version of nodejs and Chrome but got nothing.
Eventually I modified package.json with
node-html-to-image ^3
, gotERROR 54 nodejs.Error: Unable to launch browser, error message: Could not find expected browser (chrome) locally. Run
npm installto download the correct Chromium revision
.Then I run
node node_modules/puppeteer/install.js
and enerything is GOOD now.I have no idea what happened.
------ BACKGROUND ------
I use a Docker container to run my app. The base image is
node:20-bullseye-slim
and installed Chrome manually. My Dockerfile:My puppeteer args is:
The text was updated successfully, but these errors were encountered: