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

pre-push-valid

v2.0.0

Published

Checks the upstream refs during a pre-push githook

Downloads

35

Readme

pre-push-valid

Checks the upstream refs during a pre-push githook.

I've seen that many tools exist already which look at the branch name from the current working directory. This is a good first step, but it's not sufficient. The first issue is that you can push a local branch to a different remote branch by being explicit about this. A second issue is that this branch-based approach does not consider tags.

The githooks docs for pre-push mention that git provides the hook with the actual upstream refs being pushed, and this includes both branches as well as tags.

This script parses this data in order to enforce gitflow.

Convention

  • Branch names must use only lowercase characters, numbers and hyphens.
  • Only two singleton branches are allowed: master and develop.
  • Only three prefix branches are allowed: feature, release, and hotfix.
  • Prefix branches accept an arbitrary number of sub-prefixes (i.e., feature/dashboard/widget is a valid branch name).
  • Tags must conform to semver, without the leading v (i.e., 1.2.3 will be valid, v1.2.3 will be invalid).

Install

With npm do:

npm install pre-push-valid --save-dev

The easiest way to get started with githooks is via husky:

npm install husky@next --save-dev

Once it's installed, edit your package.json like so:

// package.json
{
    "husky": {
        "hooks": {
            "pre-commit": "echo \"$HUSKY_GIT_STDIN\" | pre-push-valid"
        }
    }
}

Roadmap

Right now this is a proof-of-concept, with all configuration settings hardcoded to fit my needs. This includes a few subtleties, such as disallowing v-prefixed tags.

Ideally, all of this configuration should be externalized following the current conventions. Namely:

  • A specialized section in the package.json file.
  • A dot-rc-file in json format.
  • A js file module exporting the configuration.

Also, some CLI parameters could be added for debugging, coloring, accepting input from the command-line rather than stdin, to avoid the ugly echo, etc.

If you think this is interesting please do not hesitate to contribute!

License

MIT