![]() Run `npm install` to download the correct Chromium revision (1045629). Puppeteer is a Node library which provides a high-level API to control headless Chrome or Chromium over the DevTools Protocol. Linux Relevant log output Error: Could not find expected browser (chrome) locally. ![]() Instead of specifying a download location using PUPPETEER_CACHE_DIR, is there any way the old behaviour can optionally be turned on, and let puppeteer figure out where it’s installed? This would avoid having to know the subtlety of the underlying build/file system.Ĩ.5.0 What operating system are you seeing the problem on? I’ve tried playing around with PUPPETEER_CACHE_DIR, but again, we have very little guarantees over the build flow and it potentially changing. Step 1: Install the package Install the package in your node project mkdir -p download-csv-puppeteer & npm init -y npm install puppeteer touch index. So you can pretty much do anything that you can do in the browser via code. While the Cloud Function environment is not a direct concern of the puppeteer project, the caching feature introduced in 19.0.0 makes it hard to reliably install Chromium in an environment where we don’t control the build/file system. Puppeteer provides the way to control and interact with your chrome/chromium browser via Node.js. ![]() Although the build (and probably the download of Chromium) succeeds, Chromium is not available at runtime. My guess is that the new cache location is not retained in the final Docker image for the Cloud Function. Steps to reproduce Tell us about your environment: Puppeteer version: 1.17.0 Platform / OS version: macOS 10.14.4 (18E226) Node.js version: v10.16.0 What steps will reproduce the problem sudo npm i puppeteer What is the expected result. Invoke the Cloud Function, the error below occurs.Deploy the Cloud Function, the build succeeds. Check Print-puppeteer 0.0.2 package - Last release 0.0.2 with MIT licence at our NPM packages aggregator and search engine.Depend on puppeteer 19.0.0 in a Cloud Function. ![]()
0 Comments
Leave a Reply. |