# node-chromium [![Build Status](https://travis-ci.org/dtolstyi/node-chromium.svg?branch=master)](https://travis-ci.org/dtolstyi/node-chromium) [![XO code style](https://img.shields.io/badge/code_style-XO-blue.svg)](https://github.com/sindresorhus/xo) [![npm version](https://badge.fury.io/js/chromium.svg)](https://badge.fury.io/js/chromium) [![Platforms](https://img.shields.io/badge/platforms-Win/Linux/Mac-lightgrey.svg)](https://github.com/dtolstyi/node-chromium) > Chromium binaries for your NodeJS project **node-chromium** allows you to easily add [Chromium](https://www.chromium.org/) binaries to your project and use it for automation, testing, web scraping or just for fun. ## Why Chromium? [Chromium](https://www.chromium.org/) is an open-source web browser developed and maintained by The Chromium Project. Google Chrome, also released in 2008, is a proprietary web browser developed and maintained by Google. The reason why Chrome and Chromium are tied to each other is that Chome borrows Chromium’s source code. The main benefit of using Chromium is that it **doesn't** include all the proprietary modifications made by Google, thus it's more lightweight and more suitable for automation purposes. You can see full list of differences in [Fossbytes article](https://fossbytes.com/difference-google-chrome-vs-chromium-browser/). ## Requirements Starting from version `2.2.0` `node-chromium` is tested against and supports Node.js LTS and latest stable releases Versions `2.0.0` - `2.1.2` support Node.js 7+ If you need to use older versions of Node.js try `node-chromium 1.x.x` releases. ## Usage Depending on your needs, you can install module into **devDependencies** (`--save-dev`) or production **dependencies** (`--save`) ``` npm install --save chromium ``` During the installation process **node-chromium** will find the latest suitable build for your platform, download it and extract into libraries folder. As soon as installation is finished, you are ready to use Chromium in your project: ```js const chromium = require('chromium'); const {execFile} = require('child_process'); execFile(chromium.path, ['https://google.com'], err => { console.log('Hello Google!'); }); ``` ### Proxy Configuration When downloading the chromium binary **node-chromium** will use the proxy configured for `npm` to establish HTTP(S) connections. The proxy used by `npm` can be configured using ``` npm config set proxy http://:@: npm config set https-proxy http://:@:///.zip?alt=media` for example see the taobao mirror [chromium-browser-snapshots](https://npm.taobao.org/mirrors/chromium-browser-snapshots/). * May also be set in .npmrc like so: ```ini node_chromium_download_host=https://npm.taobao.org/mirrors/chromium-browser-snapshots/ node_chromium_revision=737027 ``` ## Selenium WebDriver Headless (without UI) tests It's extremely easy to use **node-chromium** with **selenium-webdriver** to perform e2e tests without spawning browser UI. First, install all dependencies ``` npm install --save chromium chromedriver selenium-webdriver ``` After the installation is finished, create simple script that opens Google Search home page and takes it's screenshot in headless mode. ```js const fs = require('fs'); const webdriver = require('selenium-webdriver'); const chrome = require('selenium-webdriver/chrome'); const chromium = require('chromium'); require('chromedriver'); async function start() { let options = new chrome.Options(); options.setChromeBinaryPath(chromium.path); options.addArguments('--headless'); options.addArguments('--disable-gpu'); options.addArguments('--window-size=1280,960'); const driver = await new webdriver.Builder() .forBrowser('chrome') .setChromeOptions(options) .build(); await driver.get('http://google.com'); console.log('Hello Google!'); await takeScreenshot(driver, 'google-start-page'); await driver.quit(); } async function takeScreenshot(driver, name) { await driver.takeScreenshot().then((data) => { fs.writeFileSync(name + '.png', data, 'base64'); console.log('Screenshot is saved'); }); } start(); ``` ### Cache Downloaded Binaries By default downloaded chromium binaries are cached in the appropriate cache directory for your operating system. You may override the cache path by setting the `NODE_CHROMIUM_CACHE_PATH` environment variable to a directory path, for example: ```bash export NODE_CHROMIUM_CACHE_PATH=/path/to/cache/dir/ # or in .npmrc like so: # node_chromium_cache_path=/path/to/cache/dir/ ``` You may disable caching by setting `NODE_CHROMIUM_CACHE_DISABLE` to `true`: ```bash export NODE_CHROMIUM_CACHE_DISABLE=true # or in .npmrc like so: # node_chromium_cache_disable=true ``` ### Skip Automatic Chromium Install Chromium will ordinarily be installed when you exectute `npm install` however you may wish to skip this step if you are going to defer installation and perform it programatically at a later stage. Below is an example of how to do so. ```bash export NODE_CHROMIUM_SKIP_INSTALL=true # or in .npmrc like so: # node_chromium_skip_install=true ``` Then install it programatically when you need it: ```js chromium.install().then(function() { // do stuff... }); ``` ## Contributors

Rick Brown

Alex Schlosser

psociety

Daniel Hernández Alcojor

Ryan Cooney

Amila Welihinda

Timon Kurmann

Jakub Wąsik
## License MIT