Failed to launch the browser process!
See original GitHub issueI get this error when I start my next app with yarn dev
error - Error: Failed to launch the browser process! spawn C:\Program Files (x86)\Google\Chrome\Application\chrome.exe ENOENT
I have chrome installed on my system but its, not in the path printed in the error. It is in the 64bit folder. C:\Program Files\Google\Chrome\Application
My ENV
- Node 16.1.0.0
- Next 12.1.0
- chrome-aws-lambda 1.6.3
- Windows
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Error: Failed to launch the browser process puppeteer
What works for me was to download chromium manually sudo apt-get install chromium-browser . And then, tell Puppeteer where chromium is located :...
Read more >[Bug]: Failed to launch the browser process! #7917 - GitHub
An error is thrown when I use the following code! const browser = await puppeteer.launch({ headless: true });.
Read more >Troubleshooting - Puppeteer
This means that the browser was downloaded but failed to be extracted correctly. The most common cause is a bug in Node.js v14.0.0...
Read more >Puppeteer - Failed to launch the browser process! - DietPi
Puppeteer - Failed to launch the browser process! ... There seems to be a syntax error in one of the script you are...
Read more >Failed to launch the browser process! spawn puppeteer Code ...
error failed to launch the browser process puppeteer ; 1. // Puppeteer Error on ubuntu 100% Correct Solution by Vivek ; 2. wget...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@linojon I think your Problem is a different one. If you are using
Node 16.x
on Vercel try version14.x
. Because not all versions ofchrome-aws-lambda
support version16
https://github.com/neg4n/next-api-og-image/releases/tag/4.2.1