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-range-files

v1.2.0

Published

This module returns an array of git range files and their status acording to git.

Downloads

6

Readme

Git Range Files Build Status

This module returns an array of git range files and their status acording to git.

Inspired By staged-git-files.

How it works?

  • git version < 2.0.0 execute

      git diff --name-status b8c40a94db582718...813f2c4911e926c0
  • git version >= 2.0.0 execute

      git -c core.quotepath=false diff --name-status b8c40a94db582718...813f2c4911e926c0

Usage

npm install git-range-files

var grf = require('git-range-files');
grf(function(err, results) {
	// WHAT EVER YOU SO PLEASE
});

grf({ head: 'f5f240fad3f6...e87900fad3f6' }, function(err, results){
	// WHAT EVER YOU SO PLEASE
});

Example Results

[
	{
		"filename": "package.json",
		"status": "Added"
	},
	{
		"filename": "readme.md",
		"status": "Modified"
	},
	{
		"filename": "index.js",
		"status": "Renamed"
	}
]

Usage as a cli

$ grf
Added package.json
Modified readme.md
Renamed index.js

API

grf({ filter, head, relative }, callback)

Get a list of git range files from head

  • filter: string of git status codes. No spaces
  • relative: string or boolean (true by default)
    When run from a subdirectory of the project, it can be told to exclude changes outside the directory and show pathnames relative to it with this option. When you are not in a subdirectory (e.g. in a bare repository), you can name which subdirectory to make the output relative to by giving a as an argument.
  • callback:
    • err: the error
    • results: file object array.

grf.getHead(callback)

Get head that will be used in the diff to ID which files are waiting to be staged.

  • callback
    • err: the error
    • head: the git commit id which is aliased to head.

grf.readFile(filename, [options], callback)

This is a proxy for fs.readFile with one change. The filename will be relative to the grf.cwd

grf.debug

Boolean that flips logging on and off. By default this is false. If true, all git commands will be console logged.

grf.includeContent

If true, include content will add a content or err param to the file object.

  • Default Value: false
  • Content Param: the content of the file staged
  • Err Param: the error message received while trying to read the file.

grf.cwd

The current working directory. AKA: where the .git folder you care about is.

Default Value: is equal to process.cwd() of your app.g

Statuses

SGF-Status (git status code)

  • Added (A)
  • Copied (C)
  • Deleted (D)
  • Modified (M)
  • Renamed (R)
  • Type-Change (T) [i.e. regular file, symlink, submodule, etc.]
  • Unmerged (U)
  • Unknown (X)