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

phl

v1.0.1

Published

a thin wrapper around istanbul to support ava test framework.

Downloads

1,348

Readme

phl

This is a slimmer es6 version and fork of nyc

Supporting currently Mac OSX only at the time, if you want better support use nyc.

phl npm test

a code coverage tool built on istanbul that works for applications that spawn subprocesses.

Instrumenting Your Code

Simply run your tests with phl, and it will collect coverage information for each process and store it in phl_output.

phl npm test

you can pass a list of Istanbul reporters that you'd like to run:

phl --reporter=lcov --reporter=text-lcov npm test

If you're so inclined, you can simply add phl to the test stanza in your package.json:

{
  "script": {
    "test": "phl tap ./test/*.js"
  }
}

Checking Coverage

phl exposes istanbul's check-coverage tool. After running your tests with phl, simply run:

phl check-coverage --lines 95 --functions 95 --branches 95

This feature makes it easy to fail your tests if coverage drops below a given threshold.

Running Reports

Once you've run your tests with phl, simply run:

phl report

To view your coverage report:

--------------------|-----------|-----------|-----------|-----------|
File                |   % Stmts |% Branches |   % Funcs |   % Lines |
--------------------|-----------|-----------|-----------|-----------|
   ./               |     85.96 |        50 |        75 |     92.31 |
      index.js      |     85.96 |        50 |        75 |     92.31 |
   ./test/          |     98.08 |        50 |        95 |     98.04 |
      phl-test.js   |     98.08 |        50 |        95 |     98.04 |
   ./test/fixtures/ |       100 |       100 |       100 |       100 |
      sigint.js     |       100 |       100 |       100 |       100 |
      sigterm.js    |       100 |       100 |       100 |       100 |
--------------------|-----------|-----------|-----------|-----------|
All files           |     91.89 |        50 |     86.11 |     95.24 |
--------------------|-----------|-----------|-----------|-----------|

you can use any reporters that are supported by istanbul:

phl report --reporter=lcov

Including and Excluding Files

By default phl does not instrument files in node_modules, or test for coverage. You can override this setting in your package.json, by adding the following configuration:

{"config": {
  "phl": {
    "exclude": [
      "node_modules/"
    ]
  }
}}

If you need coverage for files/directories inside node_modules you can include them like so:

{"config": {
  "phl": {
    "include": [
      "node_modules/utils"
    ]
  }
}}

For a better illustration the following:

{"config": {
  "phl": {
    "exclude": [
      "node_modules/"
    ],
    "include": [
      "node_modules/utils"
    ]
  }
}}

excludes all files inside of node_modules directory other than the utils directory