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-commit-modifier

v2.0.1

Published

This module installs a commit-msg hook that will prepend a project issue number inferred from either the commit message or the current branch name. More details in the examples section below.

Downloads

6

Readme

branch-name-commit-modifier

This module installs a commit-msg hook that will prepend a project issue number inferred from either the commit message or the current branch name. More details in the examples section below.

Usage:

In your package.json add the field config and then add a subfield titled branchNameCommitModifier.

This is where you will put your options.

E.G.

{
  "name": "cool-stuff",
  "version": "1.0.0",
  "description": "this is some cool stuff",
  "main": "index.js",
  "scripts": {
    "test": "rm -rf /"
  },
  "author": "big dumb idiot face",
  "license": "MIT",
  "config": {
    "branchNameCommitModifier": {
      "preChar": "{",
      "postChar": "}",
      "projectName": "TESTPROJECT"
    }
  }
}

Options:

preChar : this is the character that will appear before the issue prefix.

postChar : this is the character that will appear after the issue prefix.

delimiter : this is the character that will appear between the project name and the issue number.

projectName : this is the name of the project that will be searched for.

Default options:

{
    preChar: '[',
    postChar: ']',
    delimiter: '-'
}

The default for projectName is any sequence of characters A-Z.

The following will match the default projectName value.

AWESOMEPROJECT
EXPLODINGcapybaras
LearnToChopOnions

The follow will NOT match the default projectName value.

AWESOME-PROJECT
E-X-P-L-O-D-I-N-G*c%a%p%y%b%a^r%a@s
1337pr0j3ct

Therefore, if you need to use something like the previous specify a value for your projectName field.

Examples:

config:

"config": {
  "branchNameCommitModifier": {
    "preChar": "{",
    "postChar": "}",
    "projectName": "TESTPROJECT"
}

current branch name TESTPROJECT-9999

commit command: commit -m "TESTPROJECT-0001 fixing issue 0001."

actual commit message value: "TESTPROJECT-0001 fixing issue 0001."

Note: since you did not include the prefix character or the postfix character it did not include them in the actual commit message.


same config & branch name as before

commit command: commit -m "updated the stuff in the files."

actual commit message value: "{TESTPROJECT-9999} updated the stuff in the files."


config:

"config": {
  "branchNameCommitModifier": {
    "preChar": "{",
    "postChar": "}",
    "projectName": "TESTPROJECT"
}

current branch name where am i

commit command: commit -m "idk what im doing lol."

actual commit message value: "{NO-ISSUE} idk what im doing lol."


More details:

The commit message value will always take precedence over the branch name value.

If there are any errors during install it may be a permissions issue as the install scripts tries to do the following:

  1. Copy the index.js into the project's .git/hooks/commit-msg
  2. Add execute permissions to the newly copied file.

Therefore, if you wish to fix any errors you can try doing the preceding steps manually.