Puppeteer not working with node 14
See original GitHub issueSteps to reproduce
Tell us about your environment:
- Puppeteer version:3.0.1
- Platform / OS version:docker (FROM:node:14.0.0-buster)
- URLs (if applicable):
- Node.js version: 14.0.0
What steps will reproduce the problem?
Please include code that reproduces the issue.
- Upgrade node image from 13.13.0 -> 14.0.0
- Run same codebase (
puppeteer.launch()
)
What is the expected result? code runs without issues, just like on 13.13.0
What happens instead?
Error: Failed to launch the browser process! spawn /opt/app/node_modules/puppeteer/.local-chromium/linux-737027/chrome-linux/chrome ENOENT
Issue Analytics
- State:
- Created 3 years ago
- Reactions:18
- Comments:15 (5 by maintainers)
Top Results From Across the Web
Troubleshooting - Puppeteer
The most common cause is a bug in Node.js v14.0.0 which broke extract-zip , the module Puppeteer uses to extract browser downloads into...
Read more >node.js - Puppeteer not working NodeJS 17 on Arch Linux
I've started working with Puppeteer and for some reason I cannot get it to work on my box. This error seems to be...
Read more >Puppeteer - npm
Puppeteer is a Node.js library which provides a high-level API to control Chrome/Chromium over the DevTools Protocol.
Read more >Runtime versions using Node.js and Puppeteer
Explains the versions of canary runtimes, libraries, and configuration information.
Read more >How to use Puppeteer inside a Docker container
If we use the Docker images for Node.js v14 LTS Gallium, when installing ... which can have compatibility issues with the latest Puppeteer....
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
Fixed by Node 14.1.0. Verified on Linux/Mac/Windows.
It looks like it’s a problem with extraction. A temporary workaround is to extract the downloaded chromium manually: