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

start-istanbul

v3.0.0

Published

Istanbul tasks for Start

Downloads

7,327

Readme

start-istanbul

npm linux build windows build coverage deps

Istanbul (ES6+ ready using Babel recently) tasks for Start.

Install

npm install --save-dev start-istanbul
# or
yarn add --dev start-istanbul

Usage

The sequence of tasks is simple: "instrument" sources, run tests, report collected code coverage and then check the result against provided thresholds (optional).

import Start from 'start';
import reporter from 'start-pretty-reporter';
import files from 'start-files';
import clean from 'start-clean';
import * as istanbul from 'start-istanbul';
import mocha from 'start-mocha';

const start = Start(reporter());

export const coverage = () => start(
  files('coverage/'),
  clean(),
  files('lib/**/*.js'),
  istanbul.instrument({ esModules: true }),
  files('test/**/*.js'),
  mocha(),
  istanbul.report([ 'lcovonly', 'html', 'text-summary' ]),
  istanbul.thresholds({ functions: 100 })
);

Instrument task relies on array of files, see documentation for details.

Arguments

instrument

istanbul.instrument(options)

report

istanbul.report(formats)

thresholds

istanbul.thresholds(thresholds)

  • thresholds{ lines, statements, functions, branches } object, {} by default

It works as check-coverage command:

Checks the coverage of statements, functions, branches, and lines against the provided thresholds. Positive thresholds are taken to be the minimum percentage required and negative numbers are taken to be the number of uncovered entities allowed.

Only defined keys will be processed, for example:

{
  statements: 100,
  functions: -10
}