npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

chromium-revision

v1.0.0

Published

Chromium binaries for Node.js projects with the ability to specify revision number

Downloads

1,819

Readme

node-chromium-revision Build Status XO code style npm version Platforms

Chromium binaries for your NodeJS project

node-chromium-revision allows you to easily add Chromium binaries to your project and use it for automation, testing, web scraping or just for fun.

Why Chromium?

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

Requirements

node-chromium-revision 2.x.x is tested against and supports Node.js 7+
If you need to use older versions of Node.js try node-chromium-revision 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-revision will find the latest suitable build for your platform (unless you specify a revision number), download it and extract into libraries folder. As soon as installation is finished, you are ready to use Chromium in your project:

const chromium = require('chromium-revision');
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-revision 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://<username>:<password>@<the.proxy.hostname>:<port>
npm config set https-proxy http://<username>:<password>@<the.proxy.hostname>:<port
npm config set no-proxy localhost,127.0.0.1,example.org

Additionally proxy settings found in the environment variables HTTP_PROXY, HTTPS_PROXY and NO_PROXY will be used if they are not defined in the .npmrc file.

Install a concrete revision

If you want to specify the revision of Chromium to be installed, just set the environment variable CHROMIUM_REVISION to the number of the revision you want to install, as in:

export CHROMIUM_REVISION=729994

Selenium WebDriver Headless (without UI) tests

It's extremely easy to use node-chromium-revision 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.

const fs = require('fs');
const webdriver = require('selenium-webdriver');
const chrome = require('selenium-webdriver/chrome');
const chromium = require('chromium-revision');
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();

License

MIT