chrome-headless-browser-docker - Continuously building Chrome Docker image for Linux.

  •        5

This repository contains three docker builds. This docker image contains the Linux Dev channel Chromium (https://www.chromium.org/getting-involved/dev-channel), with the required dependencies and the command line argument running headless mode provided.

https://store.docker.com/community/images/yukinying/chrome-headless-browser/tags
https://github.com/yukinying/chrome-headless-browser-docker

Tags
Implementation
License
Platform

   




Related Projects

taiko - A node.js library to automate chrome/chromium browser

  •    Javascript

Taiko 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.

chrome-har-capturer - Capture HAR files from a headless Chrome instance

  •    Javascript

Capture HAR files from a headless Chrome instance. Under the hood this module uses chrome-remote-interface to instrument Chrome.

navalia - A bullet-proof, fast, and reliable headless browser API

  •    TypeScript

The bullet-proof, fast, and most feature-rich Chrome driver around. Navalia lets you interact with Chrome and run parallel work with ease. Not using JavaScript? There's a GraphQL server that you can use to communicate with over HTTP allowing any runtime to drive Chrome. Simply run navalia with a specified port e.g.

serverless-chrome - 🌐 Run headless Chrome/Chromium on AWS Lambda (maybe Azure, & GCP later)

  •    Javascript

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.

chromeless - 🖥 Chrome automation made simple. Runs locally or headless on AWS Lambda.

  •    TypeScript

You can try out Chromeless and explore the API in the browser-based demo playground (source).With Chromeless you can control Chrome (open website, click elements, fill out forms...) using an elegant API. This is useful for integration tests or any other scenario where you'd need to script a real browser.


chromeless - 🖥 Chrome automation made simple. Runs locally or headless on AWS Lambda.

  •    TypeScript

You can try out Chromeless and explore the API in the browser-based demo playground (source). With Chromeless you can control Chrome (open website, click elements, fill out forms...) using an elegant API. This is useful for integration tests or any other scenario where you'd need to script a real browser.

html-pdf-chrome - HTML to PDF converter via Chrome/Chromium

  •    TypeScript

HTML 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.

headless-chrome-crawler - Distributed crawler powered by Headless Chrome

  •    Javascript

Crawlers based on simple requests to HTML files are generally fast. However, it sometimes ends up capturing empty bodies, especially when the websites are built on such modern frontend frameworks as AngularJS, React and Vue.js. Note: headless-chrome-crawler contains Puppeteer. During installation, it automatically downloads a recent version of Chromium. To skip the download, see Environment variables.

pyppeteer - Headless chrome/chromium automation library (unofficial port of puppeteer)

  •    Python

Unofficial Python port of puppeteer JavaScript (headless) chrome/chromium browser automation library. Note: When you run pyppeteer first time, it downloads a recent version of Chromium (~100MB). If you don't prefer this behavior, run pyppeteer-install command before running scripts which uses pyppeteer.

pdf-bot - 🤖 A Node queue API for generating PDFs using headless Chrome

  •    Javascript

Easily 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.

headless-devtools - Lets you perform Chrome DevTools actions from code by leveraging Headless Chrome+Puppeteer

  •    Javascript

Lets you perform Chrome DevTools actions from code by leveraging Headless Chrome+Puppeteer. Chrome DevTools is great for getting valuable information about your app 🕵️‍♂️. Using headless-devtools you can automate this process 🤖. One use-case is to collect this data over time 📈, which can help you keep your app in good health 👩‍⚕️.

puppeteer - Headless Chrome Node API

  •    Javascript

Puppeteer is a Node library which provides a high-level API to control headless Chrome or Chromium over the DevTools Protocol. It can also be configured to use full (non-headless) Chrome or Chromium. Note: When you install Puppeteer, it downloads a recent version of Chromium (~170Mb Mac, ~282Mb Linux, ~280Mb Win) that is guaranteed to work with the API. To skip the download, see Environment variables.

rendertron - A dockerized, headless Chrome rendering solution

  •    Javascript

Rendertron is a dockerized, headless Chrome rendering solution designed to render & serialise web pages on the fly. Rendertron is designed to enable your Progressive Web App (PWA) to serve the correct content to any bot that doesn't render or execute JavaScript. Rendertron runs as a standalone HTTP server. Rendertron renders requested pages using Headless Chrome, auto-detecting when your PWA has completed loading and serializes the response back to the original request. To use Rendertron, your application configures middleware to determine whether to proxy a request to Rendertron. Rendertron is compatible with all client side technologies, including web components.

sms-boom - 利用chrome的headless模式,模拟用户注册进行短信轰炸机

  •    Javascript

开启chrome的headless模式,仿真模拟用户去注册... 每一个人都可以是贡献者。 如果你发现有的网站,可以作为短信提供者,请在issue中提出,或PR.

chrome-headless-screenshots - Using headless Chrome as an automated screenshot tool (alternative to PhantomJS)

  •    Javascript

May 2018 The Chrome team has released Puppeteer, which makes much of the code in this repository obsolete. As such, this project is no longer maintained and issues have been disabled. Please check out Puppeteer. This repo contains an example implementation of using headless Chrome as an automated screenshot tool on linux, which is a common use case for PhantomJS. Contributions are welcome.

mocha-phantomjs - :coffee: :ghost: Run client-side mocha tests in the command line through phantomjs

  •    Javascript

Ariya Hidayat archived phantomjs on March 3rd, 2018. (See this tweet for more info). phantomjs served us all as great headless browser for years, but now with Electron and headless modes for both Chrome and Firefox, we have much better options. mocha-chrome is a project inspired by mocha-phantomjs, so migration should be easy, and you will be running your tests on the same browser that 50% of your users actually use! I highly recommend it. I will accept pull requests still, but I won't be answering issues or doing feature work myself.

chrome-remote-interface - Chrome Debugging Protocol interface for Node.js

  •    Javascript

Chrome Debugging Protocol interface that helps to instrument Chrome (or any other suitable implementation) by providing a simple abstraction of commands and notifications using a straightforward JavaScript API. This module is one of the many third-party protocol clients.

prerender - Node server that uses Headless Chrome to render a javascript-rendered page as HTML

  •    Javascript

Prerender is a node server that uses Headless Chrome to render HTML, screenshots, PDFs, and HAR files out of any web page. The Prerender server listens for an http request, takes the URL and loads it in Headless Chrome, waits for the page to finish loading by waiting for the network to be idle, and then returns your content. The Prerender server can be used in conjunction with our Prerender.io middleware in order to serve the prerendered HTML of your javascript website to search engines (Google, Bing, etc) and social networks (Facebook, Twitter, etc) for SEO. We run the Prerender server at scale for SEO needs at https://prerender.io/.

karmatic - 🦑 Easy automatic (headless) browser testing. Powered by Karma, Webpack & Jasmine.

  •    Javascript

A simplified zero-configuration wrapper around Karma, Webpack, Jasmine & Puppeteer. Karma, Webpack and Jasmine are all great. They're all also quite powerful and each highly configurable. When creating and maintaining small modules, duplication of these configurations and dependencies is cumbersome.