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

atlas-repo-info

v1.0.0

Published

Get basic git repository information about a directory.

Downloads

3

Readme

atlas-repo-info

Get basic git repository information about a directory.


install

npm install --save atlas-repo-info

why

This function returns basic git information about a directory, so you don't need to clutter your codebase with git-related exec or spawn calls.

examples

All you need to do is pass in the desired path to inspect, and a callback. If there is no info object passed to the callback, it means the passed directory is not a git repository. See caveats.

const getRepoInfo = require("atlas-repo-info");
const projectPath = process.cwd();
getRepoInfo(projectPath, (err, info) => {
  if (err) return console.error(err);
  if (!info) return console.log(`${projectPath} is not a repo`);
  const { gitRoot, name, dir, branch, remotes } = info;
  // full path of the root of the git project
  console.log(gitRoot)
  // name of the project's folder
  console.log(name)
  // name of the project's parent dir
  console.log(dir)
  // name of the checked-out branch
  console.log(branch)
  // hash of remote name -> url pairs
  console.log(remotes)
  // url for the "origin" remote, if it exists
  if (remotes.origin)
    console.log(remotes.origin)
})

caveats

You might run into issues if used with a bare repository (i.e. repoistories created with git init --bare). No check is currently implemented for bare repositories. It might be implemented later if I need it.