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-better-spec-reporter

v3.1.0

Published

Just a bit better spec reporter for Mocha

Downloads

5,800

Readme

mocha-better-spec-reporter

Originally it was fork for mocha own spec reporter, but it is very inconvenient to use.

Why i made fork:

  • It is possible to hide/show any part of report
  • It is possible to see where error happen - not only stack line but also relevant file content
  • It supports source maps
  • It does not show useless stack lines

Env variables usage

It is possible to hide additional stack traces via env variable MOCHA_REPORTER_STACK_EXCLUDE as glob string.

**/yadda/lib/** - will hide all of the yadda stack traces

It is possible to hide some parts of output via env variable MOCHA_REPORTER_OPTS.

hide-titles - will hide execution tests/suites titles

hide-stats - will hide stat

clear-screen - will clear the screen on start

show-back-order - will show fails in back order

Command line usage

Also it is possible to set this parameters with mocha command line option --reporter-options, e.g:

mocha -R ../../../ --reporter-options hide-stats=true,hide-titles=true test.js

You need to set options in such format A=B,C=D.... Options are:

hide-titles accepted values true|false - show/hide executed test/suites titles (default false)

hide-stats accepted values true|false - show/hide executed tests statistic (default false)

clear-screen accepted values true|false - clear the screen before executing tests (default false)

show-back-order accepted values true|false - test fails shown in back order, so first fail will be at the bottom (default true)

stack-exclude any glob string, used to match stack trace files for exclude

show-file-content it can be js or js+sm or sm, meaning what to show if available (sm - source-mapped files, js - actual files) by default it is sm

How to use

npm install --save-dev mocha-better-spec-reporter
mocha --reporter mocha-better-spec-reporter ... # and other options there
mocha -R mocha-better-spec-reporter --reporter-options hide-stats=true,hide-titles=true ...

Screenshot

screenshot