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

electron-tap

v0.1.5

Published

Electron test runner for Tape

Readme

electron-tap

Electron test runner for Tape

electron-tap

Installation

$ cd your-project
$ npm i --save-dev tape electron-tap

Usage

Define a new script in your package.json. --renderer option accepts a glob.

// ...
"scripts": {
  "test:renderer": "electron-tap --renderer 'test/**/renderer/*test.js?(x)'"
}

As an example we will test a React component. Create a new test file in directory test/renderer/Dummy-test.jsx.

// Dummy-test.jsx
import test from 'tape';
import reporter from 'electron-tap/reporter';

import React from 'react';
import ReactDOM from 'react-dom';
import ReactTestUtils from 'react-addons-test-utils';

class Dummy extends Component {
  render() {
    const style = {
      height: '60px',
      padding: '10px'
    };

    return (
      <div style={style}>Dummy component</div>
    )
  }
}

test('Dummy Component', function (t) {
  const container = document.createElement('div');
  document.body.appendChild(container);

  const component = ReactDOM.render(<Dummy />, container);
  const node = ReactDOM.findDOMNode(component);

  // assertion fails because of paddings and box-model
  t.equal(node.offsetHeight, 60, 'control height is 60px');

  document.body.removeChild(container);
  container = null;
  t.end();
});

Now run your test.

$ npm run test:renderer

This will open electron window, run all tests, output spec-like results to the Console tab in dev-tools, watch for changes in test files.