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

@fatso83/check-commit-msg

v2.0.2

Published

Check if your commit message follows Chris Beam's "Seven rules of a good commit message"

Downloads

145

Readme

@fatso83/check-commit-msg

Simple util to check that commits follow a certain template

The 7 rules of a good commit message

1. Separate subject from body with a blank line
2. Limit the subject line to 50 characters
3. Capitalize the subject line
4. Do not end the subject line with a period
5. Use the imperative mood in the subject line
6. Wrap the body at 72 characters
7. Use the body to explain what and why vs. how

Source: Chris Beams

Currently it also checks if your commit starts with a JIRA identifier (FOO-123) as well, but this is easy to fix/remove.

General Usage

npm install -g @fatso83/check-commit-msg
echo << 'EOF' > .git/hooks/commit-msg 
check-commit-msg $1
EOF
chmod +x .git/hooks/commit-msg  #make it executable

Using with Husky

If you use husky in your NPM commit hooks

 npm install -D @fatso83/check-commit-msg

Then add this to your package.json scripts' section:

    "commitmsg": "node -r '@fatso83/check-commit-msg/husky'"

Improvements welcome

Need something? Suggestions? Pull requests welcome :)