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

@zanminkian/git-hooks

v0.3.2

Published

A bundle of opinionated git hooks. All in one!

Downloads

20

Readme

@zanminkian/git-hooks

@zanminkian/git-hooks is now git-validator. Use git-validator instead.

This is a bundle of opinionated git hooks, all in one!

Replace husky, eslint, lint-staged, and commitlint in your project with this npm package.

Features

  • Unified package: Just ONE npm package to install replacing multiple.
  • Simple to use: Only two steps required; setting up scripts and installation.
  • Zero Configuration: Sensible default settings suitable for enterprise apps.

Usage

Set up the following scripts in your package.json:

  • git-hooks install: Installs hook files to {PROJECT_ROOT}/.git/hooks directory, which will check your code and commit messages after running the git commit command.
  • git-hooks format: Checks and formats all project files using the eslint --fix command.
  • git-hooks lint: Checks all project files using the eslint command.
{
  "scripts": {
    "postinstall": "git-hooks install",
    "format": "git-hooks format",
    "lint": "git-hooks lint"
  }
}

Next, install the package:

pnpm add -D @zanminkian/git-hooks

Now you can commit code to your project. Invalid code or commit messages will be automatically blocked.

How it Works

Running git-hooks install writes commit-msg and pre-commit files to the {PROJECT_ROOT}/.git/hooks directory.

  • The commit-msg file lints your git commit message before the commit is made.
  • The pre-commit file lints your staged code before the commit is made.

Advanced Usage

Working with husky

This library can work as a standalone package. However, if you have Husky 5 or a later version installed, you'll need to manually add .husky/commit-msg and .husky/pre-commit, as Husky will ignore the .git/hooks/commit-msg and .git/hooks/pre-commit:

#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

.git/hooks/commit-msg $1
#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

.git/hooks/pre-commit $1

Setup pre-push Stage

Running git-hooks install writes commit-msg and pre-commit files only. As git pre-push stage is widely used, you can run git-hooks install --pre-push <cmd> to setup git pre-push stage additionally.

{
  "scripts": {
    "postinstall": "git-hooks install --pre-push 'npm run test'"
  }
}

Customizing eslint Config

Under the hood, we use eslint to lint and format code. If you want to use a different eslint config, add your own .eslintrc.js at the root of your project. Here's an example:

module.exports = {
  rules: {
    // write your rules here
  }
}

Contributing

  • Clone this repository.
  • Enable Corepack using corepack enable (use npm i -g corepack for Node.js < 16.10).
  • Install dependencies using pnpm install.
  • Start coding and submit your PR.

Show your support

Give a ⭐️ if this project helped you!

License

MIT