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

is-dirty

v0.2.1

Published

Returns false if a git repository has no staged, unstaged or untracked changes.

Downloads

2,188

Readme

is-dirty NPM version NPM downloads Build Status

Returns false if a git repository has no staged, unstaged or untracked changes.

Install

Install with npm:

$ npm install --save is-dirty

API

var isDirty = require('is-dirty');

isDirty(directory[, globPatterns], callback);

Params

  • directory {String}: a directory that contains a .git folder
  • globPatterns {String|Array}: optionally pass one or more glob patterns to use for matching any uncommitted files. This is useful if you only want to know if specific files have not been committed.
  • callback: {Function}: function to call after the git status is returned

Usage

isDirty(process.cwd(), function(err, status) {
  console.log(status);
});
  • err: if a .git directory does not exist
  • status: if .git directory exists, and there are no staged, unstaged or untracked changes, statuswill be undefined. Otherwise status is an object with staged, unstaged or untracked changes, and matches if glob patterns are passed.

Example

Given you have a project with the following staged files:

.
├── a.txt
├── b.txt
├── c.txt
├── d.txt
└── e.txt

The following:

isDirty(process.cwd(), function(err, status) {
  if (err) return console.log(err);
  console.log(status);
});

Would result in:

{ staged:
   [ { file: 'a.txt', status: 'new file' },
     { file: 'b.txt', status: 'new file' },
     { file: 'c.txt', status: 'new file' },
     { file: 'd.txt', status: 'new file' },
     { file: 'e.txt', status: 'new file' } ],
  unstaged: [],
  untracked: [],
  matches: [] }

Matches

Pass a glob or array of globs as the second argument to return an array of matching files on the status.matches array:

isDirty(process.cwd(), ['{a,c}.txt'], function(err, status) {
  if (err) return console.log(err);
  console.log(status);
});

Would result in:

{ staged:
   [ { file: 'a.txt', status: 'new file' },
     { file: 'b.txt', status: 'new file' },
     { file: 'c.txt', status: 'new file' },
     { file: 'd.txt', status: 'new file' },
     { file: 'e.txt', status: 'new file' } ],
  unstaged: [],
  untracked: [],
  matches: [ 'a.txt', 'c.txt' ] }

About

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.

Building docs

(This document was generated by verb-generate-readme (a verb generator), please don't edit the readme directly. Any changes to the readme must be made in .verb.md.)

To generate the readme and API documentation with verb:

$ npm install -g verb verb-generate-readme && verb

Running tests

Install dev dependencies:

$ npm install -d && npm test

Author

Jon Schlinkert

License

Copyright © 2016, Jon Schlinkert. Released under the MIT license.


This file was generated by verb, v0.9.0, on July 17, 2016.