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-env-reporter

v4.0.0

Published

ci/dev environment aware mocha reporter

Downloads

4,707

Readme

mocha-env-reporter

Build Status npm version

A mocha reporter that switches output format between built-in 'spec' and customised CI reporters base on where tests are being executed - locally or ci. Actual switch is implemented by detecting an environment variable unique to each CI environment. The default is 'spec' builtin mocha reporter.

The reporter also supports an environment variable mocha_reporter in which you can set an arbitrary environment reporter. This is useful if you use an unidentified continous integration service.

Currently supported custom CI environments (see defaults.json):

  • Teamcity
  • bamboo
  • jenkins

install

npm install --save-dev mocha-env-reporter

usage

In you package.json append --reporter mocha-env-reporter to your mocha test command, ex.

...
  "scripts": {
    "test": "mocha --reporter mocha-env-reporter"
  },
...

configuration

In order to override the choice of reporter simply set environment variable mocha_reporter to the reporter name (example specs).

The default reporters per environments are defined at defaults.json

License

Licensed under MIT License.