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 🙏

© 2026 – Pkg Stats / Ryan Hefner

extelenium

v1.0.1

Published

A webdriverio wrapper that allows you to feature test your chrome plugin

Readme

Extelenium

A utility to make integration testing of chrome extensions using Webdriver.io easy

Do ever ask yourself questions like "do I have a purpose on this earth?" Or, "why am I writing a chrome extension?" or "how the hell am I supposed to test this thing?"

Try existentialenium! extelenium for short.

How it works:

Give it the directory to your chrome extension containing a manifest.json, and it will programmatically load it into a browser instance launched by Webdriver.io. It is a useful tool if you want to run integration tests continually without having to do terrible things to your wdio.conf.js every time you make a change to your extension.

EXTERNAL DEPENDENCIES:

PEER DEPENDENCIES:

Usage

1) Install extelenium

npm install --save-dev extelenium

2) Install webdriverio

3) Specify the use of chrome for running your integration tests in your wdio.conf.js file:

exports.config = {
    ...
    capabilities: [{
        ...
        browserName: 'chrome'
        ...
    }]
}

4) Install a necessary external dependency:

$ gem install crxmake

(This is used for programmatically packaging your chrome extension into crx files)

5) In a separate terminal, run a selenium server that wdio can talk to (which you should have installed during step 2)

$ selenium-standalone start

6) Use provided script to run your integration tests with your extension loaded

$ ./node_modules/.bin/extelenium --extension my-sample-extension/ --wdio-config wdio.conf.js

Setup for local Development

$ npm install -g yarn

Install dependencies:

$ yarn install

For debugging the above command

If you get an error that looks like this:

## There is an issue with `node-fibers` ##
`/Users/pivotal/workspace/web-driver-io-for-chrome-extensions/node_modules/fibers/bin/darwin-x64-51/fibers.node` is missing.

Try running this to fix the issue: /usr/local/Cellar/node/7.10.0/bin/node /Users/pivotal/workspace/web-driver-io-for-chrome-extensions/node_modules/fibers/build
ERROR: Couldn't initialise framework "wdio-jasmine-framework".
Error: Missing binary. See message above.
    at Object.<anonymous> (/Users/pivotal/workspace/web-driver-io-for-chrome-extensions/node_modules/fibers/fibers.js:20:8)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/Users/pivotal/workspace/web-driver-io-for-chrome-extensions/node_modules/fibers/future.js:2:13)
    at Module._compile (module.js:571:32)

Then try using node v6.10.*


Install external dependencies:

$ gem install crxmake

Running tests:

$ yarn all-tests

To run unit tests or feature tests only:

$ yarn unit-tests
$ yarn feature-tests