instituteposa.blogg.se

cache but it still ended up in /root/.cache The directory I was configuring it wasn't even named. In other words, I added this last step to my why is it installing it there if I'm specifying a different directory to install in with. puppeteerrc.cjs and always used the default of /.cache/puppeteer.Īt this point I had already wasted too much time trying to figure it out so I gave up and just copied the default cache directory from the base stage of the Docker container to the release stage. The resulting container did not have the cache directory I added in the. I made sure to docker-compose build a fresh empty image with no cache to guarantee that puppeteer was seeing the configuration file and using it to change its cache directory but it wasn't being picked up. Specifying a local cache directory through configuration as described in the documentation here worked locally after rm -rf node_modules and running npm i again, but for some reason it did NOT work in my Docker container 🤷‍♂️. I was not getting the error when running the app locally outside of Docker. I was getting the error above when trying to use a Puppeteer based feature in a deployed environment which runs on a Docker container. Puppeteer creates its own browser user profile which it cleans up on every run.I had the same issue and wanted to stop by and describe the solution I ended up going with in case it can help someone else. This article describes some differences for Linux users. See this article for a description of the differences between Chromium and Chrome.

See Puppeteer.launch() for more information. You can also use Puppeteer with Firefox Nightly (experimental support). const puppeteer = require ( 'puppeteer' ) Ĭonst browser = await puppeteer.

You create an instance of Browser, open pages, and then manipulate them with Puppeteer's API.Įxample: navigating to and saving a screenshot as example.png: Puppeteer will be familiar to people using other browser testing frameworks. All examples below use async/await which is only supported in Node v7.6.0 or greater. Starting from v3.0.0 Puppeteer starts to rely on Node 10.18.1+. Prior to v1.18.1, Puppeteer required at least Node v6.4.0.