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

nyc-config-common

v1.0.1

Published

A reusable nyc configuration to improve common workflow

Downloads

183

Readme

nyc-config-common

npm version Build Status

A reusable nyc configuration to improve common workflow

Installation

Use npm.

npm install --save-dev nyc-config-common

Usage

Include this package to the project's nyc configuration.

{
  "nyc": {
    "extends": "nyc-config-common"
  }
}

Then nyc command uses the better default settings whenever it's run, as described below:

On non-CI environments

  • Runs both html and text reporter in every nyc execution
  • Writes raw coverage information to coverage directory where HTML reports are also saved, instead of the default .nyc_output
    • So that users don't need to include .nyc_output to their .gitignore

On CI

For example Travis CI and AppVeyor

  • Uses text-lcov reporter by default while executing report subcommand
    • In most case nyc report is expected to print LCOV on CI to integrate coverage report services

License

ISC License © 2018 Shinnosuke Watanabe