puppeteer: Puppeteer not working with node 14
Steps 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
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 18
- Comments: 15 (5 by maintainers)
Commits related to this issue
- chore: Useful error for Node v14 breakage There is currently a bug with extract-zip and Node v14.0.0 that causes extractZip to silently fail: https://github.com/puppeteer/puppeteer/issues/5719 Rathe... — committed to puppeteer/puppeteer by jackfranklin 4 years ago
- @dr-js/core@0.3.0-dev.8 notable change: - temp-fix: ci: delay test 14.x, wait for: https://github.com/puppeteer/puppeteer/issues/5719 - fix: sanity test for `nodejs@14` - node: add TLS server session... — committed to dr-js/dr-js by dr-js 4 years ago
- @dr-js/core@0.3.0-dev.8 notable change: - temp-fix: ci: delay test 14.x, wait for: https://github.com/puppeteer/puppeteer/issues/5719 - fix: sanity test for `nodejs@14` - node: add TLS server session... — committed to dr-js/dr-js by dr-js 4 years ago
- @dr-js/core@0.3.0-dev.8 notable change: - temp-fix: ci: delay test 14.x, wait for: https://github.com/puppeteer/puppeteer/issues/5719 - fix: ci: git CRLF config & longer test timeout - fix: sanity te... — committed to dr-js/dr-js by dr-js 4 years ago
- chore: log useful error for Node v14 breakage (#5732) * chore: Useful error for Node v14 breakage There is currently a bug with extract-zip and Node v14.0.0 that causes extractZip to silently fai... — committed to puppeteer/puppeteer by jackfranklin 4 years ago
- chore(*): de-support node 8 and 11 also :arrow_up: @types/chai, @types/lodash, @types/mocha, @types/node, @types/puppeteer, @types/semver, ajv, commander, dependency-cruiser, mocha, mscgenjs, mscgenj... — committed to mscgenjs/mscgenjs-cli by sverweij 4 years ago
- chore(*): de-support node 8 and 11 also :arrow_up: @types/chai, @types/lodash, @types/mocha, @types/node, @types/puppeteer, @types/semver, ajv, commander, dependency-cruiser, mocha, mscgenjs, mscgenj... — committed to mscgenjs/mscgenjs-cli by sverweij 4 years ago
- chore(CI): Use node 13 for puppeteer. https://github.com/puppeteer/puppeteer/issues/5719 — committed to cartant/rxjs-etc by cartant 4 years ago
- chore(ci): MacOS NodeJS 14.1.0 Puppeteer NPM install issue, updated Travis conf to LTS see https://github.com/puppeteer/puppeteer/issues/5719#issuecomment-621574900 also see https://travis-ci.org/gith... — committed to daisy/ace-gui by danielweck 4 years ago
- chore: downgrade node https://github.com/puppeteer/puppeteer/issues/5719 — committed to toptal/picasso by deleted user 4 years ago
- chore: downgrade node https://github.com/puppeteer/puppeteer/issues/5719 — committed to toptal/picasso by deleted user 4 years ago
- fix: remove node@14 specific extract timeout (#5816) closes #5719 Original stream.pipeline issue has been fixed in Node 14.1.0 and above. Meanwhile, the workaround itself caused timout failures... — committed to puppeteer/puppeteer by AviVahl 4 years ago
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:
It also looks like the suspected bug might have been in Node: https://github.com/nodejs/node/pull/32968.
In which case we may have to sit tight for a Node patch release. In the mean time I’ll see if the error message from Puppeteer can be nicer.
Thanks for the debugging all; looks like
extract-zipis indeed the culprit here. It would be nice if Puppeteer gave a more helpful message than/opt/app/node_modules/puppeteer/.local-chromium/linux-737027/chrome-linux/chrome ENOENTso I’ll try to look into that.We’ll see if a fix lands in extract-zip and do some digging.
@DRoet you can install via the master branch on GitHub to get the very latest.
Can confirm it is working again on
14.1.0, but the new node14 timeout indeed fails sometimes on slower CI runs.I have opened https://github.com/puppeteer/puppeteer/pull/5732 which at least fixes the silent failures and provides a helpful message.