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 🙏

© 2025 – Pkg Stats / Ryan Hefner

git-fs-repo

v2.0.0

Published

filesystem backed git repository

Readme

git-fs-repo

filesystem-backed read-only git repository object.

ties together all of the fs-based ODB backends, and the ref discovery mechanism.

var load = require('git-fs-repo')

load('/path/to/repository/.git', function(err, git) {
  var head = git.ref('HEAD').hash

  git.find(head, function(err, obj) {

  }) 
})

API

load(dir, ready(err, repo)) -> undefined

Load a git repository from dir. ready will be called with the error (if any), and the repository object.

repo.find(Buffer | String hash, ready(err, object))

Lookup a git object from the backends. Hash must be either a 40-character hexadecimal string, or a 20-byte Buffer.

If no object was found, there will be no error, but also no data.

If there was an error in any of the backends, it will be propagated as err.

NB: find is tightly bound to the repository object, since so many other git-* projects rely on having a find function provided.

So instead of doing:

var walk = require('git-walk-tree')
  , repo = /* some repo */0;

walk(find, head_commit)

function find(oid, ready) {
  return repo.find(oid, ready)
}

You can do:

var walk = require('git-walk-tree')
  , repo = /* some repo */0;

walk(repo.find, head_commit)

repo.ref(name[, follow=true]) -> Reference

Lookup a reference by name. If follow is true or not given, it will dereference any intermediary symbolic references (i.e., refs that point at other refs.)

repo.refs([follow=true]) -> [Reference, ...]

Return all references. If follow is true or not given, it will dereference symbolic links, and the returned list will include only one reference per unique hash.

License

MIT