Repository navigation
Puppeteer not working with node 14 #5719
Description
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
Reacted by Jarrod Overson, Andrii Oriekhov, Yury Antonau, Dr, Aaron Goldenthal, Dakara, Florian Schlittenbauer, Leandro Facchinetti, Jonathan Niles, Eugene Lazutkin and 8 more
Activity
[-]puppeteer not working with node 14[/-][+]Puppeteer not working with node 14[/+]munrocket commentedon Apr 22, 2020
@DRoet only with node 14? Try
3.0.1-postDRoet commentedon Apr 22, 2020
yes I just rebuild my images using
12.16.2and that version also still worksDRoet commentedon Apr 22, 2020
how do I install this? doesn't seem to be a valid tag on the registry
jsoverson commentedon Apr 22, 2020
It looks like it's a problem with extraction. A temporary workaround is to extract the downloaded chromium manually:
nstepien commentedon Apr 22, 2020
Likely culprit: max-mapper/extract-zip#94
jackfranklin commentedon Apr 23, 2020
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.
jackfranklin commentedon Apr 24, 2020
It also looks like the suspected bug might have been in Node: nodejs/node#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.
jackfranklin commentedon Apr 24, 2020
I have opened #5732 which at least fixes the silent failures and provides a helpful message.
@dr-js/core@0.3.0-dev.8
@dr-js/core@0.3.0-dev.8
6 remaining items
leecade commentedon Apr 29, 2020
same here
AviVahl commentedon Apr 30, 2020
Fixed by Node 14.1.0. Verified on Linux/Mac/Windows.
AviVahl commentedon Apr 30, 2020
Alright, it failed once in one of our projects because of the (node14-specific) timeout that was added to the extraction process. 10s is too low for our CI.
Workaround bites back. Any chance for it to be removed, now that Node is fixed?
FYI @jackfranklin
chore(ci): MacOS NodeJS 14.1.0 Puppeteer NPM install issue, updated T…
chore: downgrade node
chore: downgrade node
DRoet commentedon May 1, 2020
Can confirm it is working again on
14.1.0, but the new node14 timeout indeed fails sometimes on slower CI runs.nstepien commentedon May 5, 2020
It's also intermittently failing for us because of the short timeout.
AviVahl commentedon May 6, 2020
@mathiasbynens saw you've just released a patch version which still has this issue. any chance for another one with the node14-specific-timeout removed? :) this is what blocks me from adding Node 14 tests to several projects.
fix: remove node@14 specific extract timeout (#5816)