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 🙏

© 2025 – Pkg Stats / Ryan Hefner

nemo-screenshot

v3.0.3-alpha.1

Published

Nemo Plugin to Use selenium-webdriver to take a screenshot

Readme

nemo-screenshot

Nemo plugin which uses selenium-webdriver to take a screenshot

Register as "screenshot" (see below)

Build Status

Requirements

  • Lists nemo@^1.0.4 as a peerDependency

Usage

  • npm install --save-dev nemo-screenshot@^v1.0.0
  • Add this to your Nemo plugins configuration (adjust arguments according to where you want screenshots to be saved):
plugins: {
  screenshot: {
    module: 'nemo-screenshot',
    arguments: [reportPath {String}[, eventArray {Array}]]
  },
  /* other plugins */
},
driver: {
  // driver props
}

The plugin takes as argument the path to save the screenshots and an optional eventsArray. The events array can have one or more of the following elements.

  • "click" - Takes a screenshot everytime the user performs a click
  • "exception" - Takes a screenshot when an exception occurs

API

screenshot.snap

  • @argument filename {String} will save <report directory>/filename.png to the filesystem
  • @returns {Promise} resolves to a JSON object:
{
  "imageName": "myImage.png",
  "imagePath": "/path/to/image/"
  // this will be included optionally if Jenkins environment variables are present
  // "imageUrl": "jenkinsURL",
  // "archivedImageUrl": "jenkinsURL"
}

screenshot.done

This is a convenience wrapper around screenshot.snap which can accept a callback, e.g. a mocha done method

  • @argument filename {String} will save <report directory>/filename.png to the filesystem
  • @argument done {Function} errback function to execute after screenshot is saved (or if there is an error saving screenshot)
  • @argument err {Error} (optional) error associated with screenshot. image information will be attached to this error's stack trace for reporting purposes

Usage example:

  it('will do some stuff then take a screenshot', function (done) {
    nemo.somePlugin.someAction().then(function() {
      // success!
      nemo.screenshot.done('success', done);
    }, function (err) {
      // failure!
      nemo.screenshot.done('success', done, err);
    });
  });

screenshot.setCurrentTestTitle

If set, the test title will be used as the screenshot filename when an exception occurs. Default screenshot filename is ScreenShot_onException-[process_id]-[timestamp].png, which is not easy to identify the failing test case.

  • @argument testTitle {String} current test title