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

contrib-locs

v0.2.1

Published

a CLI util/git hook to count total line of code contributed to a repo for each git user

Downloads

17

Readme

contrib-locs

a CLI util to keep a list of all people who are to blame for all the the inidividual lines in the codebase. This can be used to roughly compare contribution volume between all the comitters.

Install

npm i contrib-locs -g

it stores the ledger inside the repo in json format. It can look like this:

{
  "lastCommit": "aaaaa",
  "contributors": [
    {
      "email": "[email protected]",
      "loc": 299,
      "total_additions": 247,
      "total_deletions": 52,
      "percentageOfTotal": 100
    }
  ]
}

It counts all the lines added/removed in all commits, so the line is counted even if it was removed later.

There are two command

  • init
  • preCommit

First run

invoke contrib-locs init in your project repo root.

Set up githooks with husky

Here's an example husky(7.x.x) CLI command to use to set up git hook to update contributors before each commit:

 npx husky add .husky/pre-commit "contrib-locs preCommit"

Config

Is defined in the root of your git repo in a file .contrib-locs file. File format is JSON5. Default config looks like this:

{
  matchFiles: ['*', '!contrib-locs.json'],
  matchUsers: ['*', '!*[bot]@users.noreply.github.com'] // filters out github bots
}

Including/excluding files

You will most likely want to ignore certain files. Like for example files that are generated code. By default contrib-locs only works on files that are in git, so if such files are in .gitignore there's no additional config needed. If you want to exclude/include files in git add matchFiles

For example if you only want to count files that are typescript files and markdown, you can use this:

{
  matchFiles: ['**/*.ts', '**/*.tsx', '**/*.md']
}

match is used as param for micromatch so you can also negate if needed. Like if you want to count all files except json:

{
  matchFiles: ['*', '!**/*.json']
}

Including/excluding users

{
  matchUsers: ['*@uber.com', '!*[bot]@users.noreply.github.com'] // only people from uber domain will get counted, bots will be ignored
}

contributions from unmatched users are skipped. They don't even count into the totalLinesAddedOrRemoved.