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

stdout-reporter

v1.0.0

Published

A tests stdout reporter

Downloads

15

Readme

stdout-reporter

A tool to report test results on node's stdout.

Build Status

Install

npm install --save-dev stdout-reporter

Usage

var Reporter = require( "stdout-reporter" );
var reporter = new Reporter( [ options ] );

/* and then you set your logging methods */
...

Logging Methods

  • moduleStart: register a module start
    • requires a details object as the argument with the following properties:
      • name: the module's name
  • testStart: register a test start
    • requires a details object as the argument with the following properties:
      • name: the test's name
  • assertion: register an assertion execution
    • requires a details object as the argument with the following properties:
      • module: a string with the module's name
      • name: a string with the test's name
      • result a Boolean value for the result (true if passed)
      • message: a string with the assertion's message
      • source: [optional] a string with the the stacktrace information
      • actual: the assertion given value to be compared with the expected object
      • expected: the expected value
  • testDone: register a test ending
    • requires a details object as the argument with the following properties:
      • failed: a number with the failed assertions in the test
      • runtime: a number representing the runtime in ms
  • done: register a run ending
    • requires a details object as the argument with the following properties:
      • total: a number with the total assertions
      • failed: a number with the failed assertions
      • passed: a number with the passed assertions
      • runtime: a number representing the runtime in ms

Options

This module can be instatiated with an options object as its argument.

  • output: none (default), "minimal" or "verbose"
    • with no given value, the default output will list the modules and test names, followed by dots representing each passing assertion.
    • minimal will omit the modules and tests names on the output.
    • verbose will print a more detailed output.