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

git-diff-code-coverage

v3.0.1

Published

Application used to check code coverage by tests on added lines (ex. check coverage just on new code in PR)

Downloads

53

Readme

Git Diff Code Coverage

Build Status airbnb-style npm version

Application used to check code coverage by tests on added lines (ex. check coverage just on new code in PR)

How to use?

  1. Install tool
npm i -g git-diff-code-coverage
  1. Run test to generate coverage report
npm test
  1. Run application to analyze it
gitDiffCodeCoverage --repoPath=/Users/user/Src/example --reportPath=artifacts/coverage/coverage-summary.json --fileTemplate=app/**/*.js --source=newBranch --target=master --reportFormat=lcov -v

Arguments

Path to folder with initiated git repository (required)

--repoPath, String

Source branch or commit hash (ex. myCoolFeature)

--source, String

Target branch or commit hash (ex. master)

--target, String, defaultValue: 'master'

Path to generated report (json summary coverage report)

--reportPath, String, defaultValue: 'coverage/coverage-summary.json'

Verbose mode (display stats by each file and line)

--verbose, -v

Silent mode (hide all output)

--silent, -s

Minimum overall coverage

--minimumOverallCoverage, -m, Number, defaultValue: 70

Files to analyze

--fileTemplate, -f, String, defaultValue: 'src/**/*.js'

Report format

--reportFormat, String, defaultValue: 'lcov', possible values: 'json', 'lcov'

Areas to improve:

  • Analyse git default output (using data between @@ ... @@)
  • Add other coverage report support
  • Improve coverage
  • Generate pretty output