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

protractor-e2e-coverage

v1.3.0

Published

Protractor plugin for E2E coverage

Downloads

36

Readme

Protractor e2e coverage

A plugin for Protractor to measure e2e coverage

Install

npm install protractor-e2e-coverage

Usage

in your protractor conf file add this:

  plugins: [
    {
      path: '../node_modules/protractor-e2e-coverage/index.js',
      outdir: 'test/coverage'
    }
  ],

Options

coverage setup comes predefined with what elements and events to listen to and report. it's possible to set this up with the following command

  plugins: [
	{
      elements: [ 
      	// add one for each DOM type
        {
          'type': 'button',
          'events': ['click'], // array of events to listen to
          'elements': []
        }
      ]
  }

Current DOM element and event setup

| Elements | Events | | | | | | | |----------|--------|-------|---------|-------|------|--------|--------| | Button | - | Click | - | - | - | - | - | | Form | - | - | - | - | - | - | Submit | | Input | Input | Click | Invalid | Focus | Blur | Change | - | | Select | - | Click | - | - | - | Change | - | | Textarea | Input | Click | - | Focus | Blur | Change | - | | A | - | Click | - | Focus | Blur | - | - |

What it is

Runs after your tests to see which elements on the page has been interacted with. If coverage in unit is measuring visited logic, then this can be seen as visited elements.

What the user sees, the user should be able to interact with

It essentially detects events on certain elements