12 best open source headless chrome projects.

We have collection of more than 1 Million open source products ranging from Enterprise product to small libraries in all platforms. We aggregate information from all open source repositories. Search and find the best for your needs. Check out projects section.

Displaying 1 to 12 from 12 results

lighthousebot - Run Lighthouse in CI, as a web service, using Docker. Pass/Fail GH pull requests.

Javascript

This repo contains the frontend and backend for running Lighthouse in CI and integration with Github Pull Requests. An example web service is hosted for demo purposes. Note: This repo was previously named "lighthouse-ci".

lighthouse ci pwa testing headless-chrome travis docker

lighthouse-ci - Run Lighthouse in CI using Docker

Javascript

This repo contains the frontend and backend for the Lighthouse CI server. Please note: This drop in service is considered Beta. There are no SLAs or uptime guarantees. If you're interested in running your own CI server in a Docker container, check out Running your own CI server.

lighthouse ci pwa testing headless-chrome travis docker

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.

testing-tools headless headless-browsers headless-chrome headless-chromium headless-testing automation headless-browser

chrome-remote-multiplex - Allows multiple Chrome DevTools Clients to simultaneously connect to a single Remote Debugger (ie Chrome Headless) instance

Javascript

Proxy 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

codepen-puppeteer - Use Puppeteer to download pens from Codepen.io as single html pages

Javascript

Use Puppeteer to download pens from Codepen.io as single html pages. Need help or have a question? post at StackOverflow.

puppeteer codepen web-scraping headless-chrome scraping node chrome-headless

act-page-analyzer - Apify actor that opens a web page in headless Chrome and analyzes the HTML and JavaScript objects, looks for schema

Javascript

When analysis is finished it checks INPUT parameters if there are any strings to search for and if there are. Then it attempts to find the strings in all found content. The act ends when all output is parsed and searched. If connection to URL fails or if any part of act crashes, the act ends with error in output and log.

headless-chrome web-scraping apify apifier crawler search

apify-js - Apify SDK: The ultimate web scraping and automation library for JavaScript / Node

Javascript

The package provides helper functions to launch web browsers with proxies, access the storage etc. Note that the usage of the package is optional, you can create acts on Apify platform without it. If you deploy your code to Apify platform then you can set up scheduler or execute your code with web API.

web-scraping web-crawling javascript-library npm headless-chrome puppeteer apify headless chrome selenium crawler scraper

proxy-chain - Node

Javascript

Node.js implementation of a proxy server (think Squid) with support for SSL, authentication, upstream proxy chaining, custom HTTP responses and measuring traffic statistics. The authentication and proxy chaining configuration is defined in code and can be dynamic. Note that the proxy server only supports Basic authentication (see Proxy-Authorization for details). For example, this package is useful if you need to use proxies with authentication in the headless Chrome web browser, because it doesn't accept proxy URLs such as http://username:password@proxy.example.com:8080. With this library, you can setup a local proxy server without any password that will forward requests to the upstream proxy with password. For this very purpose the package is used by the Apify web scraping platform.

javascript-library proxy-server proxychains headless-chrome proxy squid apify tunnel

after-work.js - CLI for automated tests in web projects.

Javascript

after-work.js is an unified test framework highly configurable through cli and configuration files allowing tests to be executed in the desired context. after-work.js aims to be a tool that facilitates the testing while development or restructuring code. Designed for test and provide fast feedback on changed code and added testcases.

qlik test-framework headless-chrome command-line-tool mocha-tests mocha-chai mocha-chai-sinon painless-javascript-testing testing developer-experience puppeteer protractor

serverless-lighthouse-template - Run lighthouse audits from headless chrome in lambda.

Javascript

Using headless Chrome and Lambda, Serverless Lighthouse analyzes web apps and web pages, collecting modern performance metrics and insights on developer best practices. Install the required packages.

template headless-chrome chrome example datadog datadog-metrics