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

branch-name

v1.0.0

Published

Get the current branch name

Downloads

48,700

Readme

branch-name Build status for branch-name

Get the current branch name

Why?

  • Clean, minimal, promise-based API.
  • Respects your $PATH.
  • Uses the most reliable branch detection algorithm.
  • Gives you control in weird situations.

Install

npm install branch-name --save

Usage

Get it into your program.

const branchName = require('branch-name');

Get the current branch name.

branchName.get().then((name) => {
   console.log(name);
});

Get the current branch name, but with a fallback result for detached head and non-repository situations.

branchName.assume('dev').then((name) => {
   console.log(name);  // prints current branch if possible, 'dev' otherwise
});

Get the current branch name, with the default master as a fallback.

branchName.assumeMaster().then((name) => {
   console.log(name);  // prints current branch if possible, 'master' otherwise
});

API

get(option)

Returns the branch name that HEAD points to. Throws an error if not in a git repository or HEAD is not a branch.

assume(name, option)

Similar to .get(), but will return name if not in a git repository or the HEAD is detached.

assumeMaster(option)

Similar to .assume() but always uses "master" as the fallback name.

option

Type: object

cwd

Type: string Default: process.cwd()

Directory whose branch you want determine.

Related

Contributing

See our contributing guidelines for more details.

  1. Fork it.
  2. Make a feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request.

License

MPL-2.0 © Seth Holladay

Go make something, dang it.