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 🙏

© 2026 – Pkg Stats / Ryan Hefner

honey-git-flow

v0.1.0

Published

A new git flow with hooks for waffle.io. And now you have a Waffle with honey.

Readme

honey-git-flow

A new git flow with hooks for waffle.io. And now you have a Waffle with honey.

Configure

Init

You need create in your root folder a gitValidations.json

{
    "branchMasters": [
        "master",
        "develop"
    ],
    "branchNames": [
        "feature/#ID_ISSUE/shortest_description",
        "fix/#ID_ISSUE/shortest_description"
    ],
    "commit": {
        "pattern": "<type>(<scope>): <subject>",
        "rules": [
            {
                "type": "regex",
                "rule": "feature|fix|refactor|test|chore",
                "message": "Missing commit (feature, fix, refactor, test or chore)."
            },
            {
                "rule": ":",
                "message": "Missing colon (:)"
            }
        ]
    }
}

BranchMasters: It's a property reference for name of your branchs without pattern. BranchNames: It's a property reference for name of your branchs with pattern. Commit: It's a template of your commit pattern.

(remembering that it is necessary everywhere the ids of the issue)

Pre-commmit

Add in scripts of your package.json

"commitmsg": "node node_modules/honey-git-flow/gitValidations.js commit"

Rebase Blocker (Its a extra)

"prerebase": "node node_modules/honey-git-flow/gitValidations.js rebase"

*** We have a issue #3 to create a CLI to trigger this in another way ***

Usage

Example of commit message

git commit -m "feature(new-table) | we develop a new table"

Ps.: This example apply Karma Pattern.

Example of branch name

feature/#000/test-feature
fix/#000/test-feature
test/#000/test-feature

Example of PR name

closes #000 | test message

Ps.: We can use Github's helper as prefix in yours PR's

Common problems

If your ghooks not triggered, you need to delete .git/hooks. And re-install the ghooks of husky using $ node node_modules/husky/bin/install.js