Connect to my local 802.11n 2.4GHZ SSID.URLs (if applicable): (the chromium artifact being downloaded).Platform / OS version: Linux, 64bit, Ubuntu 19.10.I'm worried you won't be able to replicate the issue, but I will provide as much as possible data so that it might be possible to find the bug inside the code despite not being able to replicate it on your own machine. being connected to a 5GHz 802.11ac SSID configured on the same wifi access point, the npm install puppeteer works as expected.Įven it looks like the culprit might be in the misconfigured AP or some weird network connection/configuration, I think, the real culprit lies somewhere in the install scripts: install.js / BrowserFetcher.js, where downloading the last chunk of the chromium browser somehow never finish.the issue only occurs when I'm connected to a 802.11n 2.4GHz wifi SSID.Despite having solution, I can reliably replicate the issue. I couldn't believe there is any magic involved so I decided to troubleshoot it and found a solution to install the module on my environment without the installation hanging. The same has been already reported in #4688, but closed as automagically solved. I'm experiencing one weird issue with npm install puppeteer - the installation idenfinitely hangs on Downloading Chromium r662092 - 111.6 Mb 99% 0.0s.

Download node puppeteer for free