Serverless Chrome contains everything you need to get started running headless Chrome on AWS Lambda (possibly Azure and GCP Functions soon). Why? Because it's neat. It also opens up interesting possibilities for using the Chrome DevTools Protocol (and tools like Chromeless or Puppeteer) in serverless architectures and doing testing/CI, web-scraping, pre-rendering, etc.
serverless serverless-framework aws aws-lambda chrome headless-chrome chrome-debugging-protocol lambda chromium headless-chromium serverless-plugin serverless-functions chrome-devtools-protocol serverless-examples headlessEasily create a microservice for generating PDFs using headless Chrome. pdf-bot is installed on a server and will receive URLs to turn into PDFs through its API or CLI. pdf-bot will manage a queue of PDF jobs. Once a PDF job has run it will notify you using a webhook so you can fetch the API. pdf-bot supports storing PDFs on S3 out of the box. Failed PDF generations and Webhook pings will be retried after a configurable decaying schedule.
html pdf headless headless-chrome pdf-generator nodejs node-js pdf-generation chromium headless-chromium google-chromebrowserless is an efficient driver for controlling headless browsers built on top of puppeteer developed for scenarios where performance matters. browserless is backed by puppeteer, so you need to install it as well.
headless-chrome headless-chromium puppeteer puppeteer-core browser browserless chrome chromeless headless html pdf screenshot textTaiko is a free and open source browser automation tool built by the team behind Gauge from ThoughtWorks. Taiko is a node library with a clear and concise API to automate the chrome browser. Tests written in Taiko are highly readable and maintainable. Taiko’s smart selectors make tests reliable by adapting to changes in the structure of your web application. With Taiko there’s no need for id/css/xpath selectors or adding explicit waits (for XHR requests) in test scripts.
testing-tools headless headless-browsers headless-chrome headless-chromium headless-testing automation headless-browserHTML to PDF converter via Chrome/Chromium. Note: It is strongly recommended that you keep Chrome running side-by-side with Node.js. There is significant overhead starting up Chrome for each PDF generation which can be easily avoided.
chrome chromium html html-pdf-chrome pdf pdf-generation typescript headless-chrome headless-chromium headless-browsers headless nodejs node-js google google-chrome pdf-generator html-pdf macProxy Server application which allows multiple Chrome DevTools Clients to simultaneously connect to a single Remote Debugger (ie Chrome Headless) instance. Google Chrome Headless (or any other Devtools Protocol implementation) only allows one client to control it at any particular time; this means that if you have an application which uses chrome-remote-interface to operate the web page, you cannot debug that web page while it is being controlled by your application.
chrome-debugging-protocol chrome-devtools headless-chrome headless-chromium headless-server nodejs chrome debug protocol remote interface headless
We have large collection of open source products. Follow the tags from
Tag Cloud >>
Open source products are scattered around the web. Please provide information
about the open source projects you own / you use.
Add Projects.