But is that where the differences end? Is it apples and oranges? More like crocodiles and alligators 🐊 Puppeteer ended up as a Chromium-centric and established Google solution Playwright ended up as more cross-browser, and the more recent library brought to you by the Microsoft team. RUN node node_modules/puppeteer/install.You’re probably familiar with how the legend goes: at some point in 2020, the Puppeteer team transformed into the Playwright team, and now we’re stuck here trying to pick one of these great libraries to automate actions in a browser or test a web page. T05:46:28.039Z a251301b-87b7-4e34-bf7c-c1d0a42ae6f5 ERROR ProtocolError: Protocol error (tAutoAttach): Target closed.Īt /var/task/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:104:24Īt nd (/var/task/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:100:16)Īt ChromeTargetManager.initialize (/var/task/node_modules/puppeteer/lib/cjs/puppeteer/common/ChromeTargetManager.js:253:82)Īt Browser._attach (/var/task/node_modules/puppeteer/lib/cjs/puppeteer/common/Browser.js:219:73)Īt Function._create (/var/task/node_modules/puppeteer/lib/cjs/puppeteer/common/Browser.js:201:23)Īt ChromeLauncher.launch (/var/task/node_modules/puppeteer/lib/cjs/puppeteer/node/ChromeLauncher.js:92:50)Īt processTicksAndRejections (internal/process/task_queues.js:95:5)Īt async generatePdf (/var/task/dist/src/helpers/makePdf.js:21:21)Īt async Runtime.pdf (/var/task/dist/src/generate.js:21:29) Sh -c 'echo "deb stable main" > /etc/apt//google.list' & \Īpt-get install google-chrome-stable -y -no-install-recommends & \įROM /lambda/nodejs:14.2022.09.09.11 Wget -quiet -output-document=- | gpg -dearmor > /etc/apt//google-archive.gpg & \ RUN apt-get update & apt-get install gnupg wget -y & \ # Note: this installs the necessary libs to make the browser work with Puppeteer. That's why we prefer Debian variants to make it easier.Įvery major version of Node.js in built over a version of Debian, and that Debian version comes with an old version of Chromium, which one could be not compatible with the latest version of Puppeteer.ĮNV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD true Yeah, we can run Chromium using Alpine Linux, but we'll need a few extra steps to make it run. it's important to know what are the different between the available variants. we want to run a web browser inside a container. This is because it was tested with the latest Chromium stable release.
If we use the Docker images for Node.js v14 LTS Gallium, when installing the chromium package from apt, it will be v90.0, which can have compatibility issues with the latest Puppeteer. This guide helps to use Puppeteer inside a Docker container using the Node.js image. Puppeteer is a Node.js library which provides a high-level API to control Chromium (or Firefox) browsers over the DevTools Protocol.
0 kommentar(er)
