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

mocha-yar

v2.0.1

Published

Yet Another Reporter for Mocha

Downloads

1,001

Readme

mocha-yar

NPM downloads

Yet Another Mocha Reporter

A Mocha test reporter designed to be more useful for continuous testing, including:

  1. Running counts of passed / failed / total tests
  2. Wrapping of console.log so that:
    1. You can actually see logs
    2. They don't interfere with live counts (much)
    3. You can tell where the logs come from (!!)
  3. Mad colorz, yo!
  4. Enable timing of tests:
    1. Via config: time: "test,total"
      • test will output timing after every test, so you'll lose the continual feel
      • total will output total test time at the end of the run
    2. Via environment variables: TIME_TEST and TIME_TOTAL
      • you can use the special values "true", "false", "1" and "0" or any truthy value
    3. Environment variables override config, if the config exists

What you get

  • Yet another Mocha reporter
  • Happy tests run past with minimal output
  • Sad tests are reported at the end of the run (or immediately, if impatient is set)
  • Output from tests is labelled with the test which creates the output
    • Never wonder again where that stray console.log is!
    • Output can be suppressed per-test via suppressOutputFrom
  • console.error output is highlighted with white-on-red

See the test gulpfile in this repo for configuration examples

Example output:

Happy path

Happy output

Mixed path

Mixed output

What you don't get

Any kind of guarantee that this is the code you're looking for

What you can do

  1. Keep all pieces if it breaks
  2. Modify and redistribute it, with kudos, of course

Why? There are so many other reporters!

You're right. None that I found gave me (karma / jasmine)-like feedback whilst running. No runner that I've seen helps you to hunt down rogue console.log() calls. Other than that, this is totally pointless. Feel free to tell your friends how pointless it is! They will surely be impressed.