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

@jshawl/pre-commit

v0.1.2

Published

Pre-commit guards

Downloads

28

Readme

Pre-Commit Hook

This npm package generates a git pre-commit hook that runs a set of customizable bash commands.

Philosophy

No package.json changes

Local commits are a very personal activity. Your own commit guards don't need to be shared with other contributors to your repository.

Not npm specific

This package's runtime is nodejs but you can add arbitrary bash commands as commit guards:

.pre-commit-scripts:

npm run format:check
npm run format # format anyway to pass the next check
npm run lint
! git diff --staged | grep console.log # prevent accidentally sharing debug statements

Index safe by default

No changes are ever applied to the staging area programmatically.

The general workflow is:

  1. Try to commit
  2. See commit guard errors
  3. Fix errors
  4. Stage changes
  5. Try to commit (and succeed this time)

Install

npm install @jshawl/pre-commit

A post-install script will copy a pre-commit executable to .git/hooks/pre-commit.

Usage

git commit --allow-empty -m "testing pre-commit hook"

A few npm scripts will run. If any of them fail, git will not commit. You can skip the pre-commit hook by adding the --no-verify to a git commit command.

Configuration

It's possible to override the default commands.

Create a .pre-commit-scripts file like this one:

npm run format:check
npm run format
npm run lint
npm run build

in your repository's root directory, and list whichever commands you want to exit 0 before allowing a commit.

Optionally, consider ignoring this file so other contributors to the repository don't have to follow your own commit rules:

echo .pre-commit-scripts >> .git/info/exclude

Uninstall

npm uninstall @jshawl/pre-commit

or just remove the pre-commit hook:

rm .git/hooks/pre-commit