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-clone-or-pull

v4.0.0

Published

Ensure a git repo exists on disk and that it's up-to-date

Downloads

9

Readme

git-clone-or-pull

Build Status Coverage Status npm Greenkeeper badge

Ensure a git repo exists on disk and that it's up-to-date

Installation

npm install git-clone-or-pull

Node 4.x or greater is required. The module will probably work on Node 0.12, but the tests do not. So I wouldn't count on it.

Usage

Simple example:

var cloneOrPull = require('git-clone-or-pull');
var path = require('path');

cloneOrPull('git://github.com/strugee/node-git-clone-or-pull.git', path.join(process.cwd(), 'node-git-clone-or-pull'), function(err) {
    if (err) throw err;

    // Use repo
});

The cloneOrPull() function takes three arguments. In order:

url (String) - the URL to clone from

opts (String or Object) the pathname to clone to if a String, otherwise an object containing module options (see "Options" below)

callback (Function) function callback that will be called upon completion of the clone or pull. If there is an error, it will be passed as the first argument.

Options

path (String) - the pathname to clone to. If a String is provided instead of an options Object, it will be used as path's value.

implementation (String) - the implementation to use; defaults to nodegit in most cases (see "Implementations" below)

branch (String) - the branch to use; defaults to master (even if the default upstream branch is something else)

Implementations

  • nodegit uses NodeGit, the libgit2 bindings for Node.
  • subprocess is based on spawning git subprocesses (which means you need a git binary installed).

Implementation is determined with the following algorithm:

  1. If opts.implementation exists its value will be used as the implementation; if that implementation is unavailable an error will be returned to the callback
  2. If NodeGit can be loaded, the implementation will be nodegit
  3. If git --version returns an exit code of 0, the implementation will be subprocess
  4. No implementation can be found and an error will be returned to the callback

Each implementation has its negatives: nodegit makes installation slightly more complicated. subprocess works on most systems - but it requires an external binary.

License

LGPL 3.0+

Author

AJ Jordan [email protected]