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

gitopia

v1.0.0

Published

Yet another Git wrapper.

Downloads

7

Readme

Git Utils

git-utils is yet another Git wrapper (yes, I thought about calling it yag or something similar, but that joke's a little played out, I think). So why another Git wrapper? Mainly because I looked at all the existing ones and they didn't do what I need, and I didn't feel that they were well-suited for contribution. Which is why I'm rolling my own. My goals are:

  • Extremely easy to create new functions.
  • Write one (synchronous) function, and the framework will automatically generate sync and (promise-based) async versions.
  • Fast, easy unit testing.

Sync/Async

The full API is available sync and async versions. The only difference is that the async version returns promises. To use the sync version:

const git = require('gitopia')().sync

// example usage:
const commits = git.commits()

To use the async version:

const git = require('gitopia')()

// example usage:
git.commits(commits => console.log(commits))

Working Directory

By default, gitopia assumes the current working directory is part of the desired repository. To change this or make the working directory explicit, use the workdir option:

const git = require('gitopia')({ workdir: '/path/to/your/repo' ))

API

For simplicity, all examples use sync API.

  • Get information about all commits: commits()
  • Get all tags and their associated commit: tagsWithCommit() (array) or commitsByTag() (object map)
  • Get all valid semver tags and their associated commit: semverTagsWithCommit() (array) or commitsBySemver() (object map)
  • Determine if working directory or index is dirty: isDirty(). Note that untraced files, by default, do not indicate a dirty working directory. To change this, use strict option: isDirty({ strict: true }).