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

ghk

v1.0.3

Published

write git hooks using nodejs

Downloads

21

Readme

ghk

write git hooks using nodejs

installation

to use ghk, you need to install it globally

$ npm install -g ghk

as well as locally in your project directory

$ npm install --save-dev ghk

usage

cd into your git repository and run

$ ghk init

to setup default git hooks for that repository

plugins

ghk does not actually do anything rather than to setup git hooks and call the appropriate ghk plugins. its the plugins that do the actual processing

currently, these plugins are available:

to use a plugin, you need to install them locally in your project:

$ npm install --save-dev PACKAGENAME

and then specify in your .ghkrc file (can be located in your project's root directory or your home directory):

{
    "pre-commit": {
        "branch-nocommit": {
            "branches": ["master"]
        },
        "jshint": {}
    }
}

.ghkrc

the keys of the .ghkrc file corresponds to the names of the git hooks in which they will be executed. the available git hooks are:

  • applypatch-msg
  • commit-msg
  • post-update
  • pre-applypatch
  • pre-commit
  • pre-push
  • pre-rebase
  • prepare-commit-msg
  • update

if you want a package to execute at a certain git hook, simply add it and its configuration to the appropriate key in .ghkrc. generally, the format of the .ghkrc file looks like this:

{
    "git-hook-name": {
        "package-name": {
            "package-config": "value",
            "package-config": "value"
        },
        "package-name": {}
    }
}

creating plugins

ghk plugins are just npm modules which exposes an API corresponding to the git hook names that it supports. for example, if a ghk plugin supports a pre-commit hook, its API would look like this:

exports['pre-commit'] = function() {
    // plugin implementation here
};

the plugin should return true if it succeeds. otherwise, it should return an error message explaining why it failed.