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

gitp

v0.1.1

Published

A git proxy (or decorator (if you will)) that allowes doing custom work for git commands before sending the commands to git. Only command affected right now is the `commit` command.

Downloads

2

Readme

gitp

A git proxy/(decoratorish) module for prefixing your commit messages with the story id from your branch name.

Installation:

  • First: npm install -g gitp
  • Then (from your projects root directory): npm install gitp

Usage:

gitp commit -a -m "Some commit message here."

For example branch 'b07898-hello-world-feature' the following call will produce commit message "B-07898 - Some commit message here.":

gitp commit -a -m "Some commit message here."

And for branch 'd08432-some-defect-fix-branch' the following message will be produced: "D-08432 - Some commit message here."

Note All git commit flags supported except -- followed by files (-- <files>). For this scenario use git add first then after adding your files use gitp commit <flags>.

The story id format is hard-coded in the code but can be changed to live in a config file later. The story id format expected in the branch name is: /^[a-z](\-|_)?\d+/i; E.g., b01234-hello_world_branch or d1984-fix-for-some-defect

Resources:

  • git help commit
  • http://git-scm.com/docs/git-commit
  • http://stackoverflow.com/questions/1417957/show-just-the-current-branch-in-git

License:

  • MIT License (http://opensource.org/licenses/MIT)