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

@tofrankie/commitlint

v0.0.6

Published

Shared Commitlint configuration

Readme

@tofrankie/commitlint

npm version node version npm package license npm last update

Shared commitlint configuration.

[!IMPORTANT] Before 1.0.0, releases may include breaking changes. Read the CHANGELOG before upgrading.

Quick Start

Install dependencies:

$ pnpm add @commitlint/cli @tofrankie/commitlint -D

Create a commitlint.config.js in your project root:

export default {
  extends: ['@tofrankie/commitlint'],
}

See the Commitlint rules reference for all rule options.

Example: custom scope-enum:

export default {
  extends: ['@tofrankie/commitlint'],
  rules: {
    'scope-enum': [2, 'always', ['foo', 'bar']],
  },
}

Using with simple-git-hooks and lint-staged

Install dependencies:

$ pnpm add simple-git-hooks lint-staged -D

Add simple-git-hooks to package.json:

{
  "simple-git-hooks": {
    "pre-commit": "pnpm lint-staged",
    "commit-msg": "pnpm commitlint --edit $1"
  }
}

After you change this configuration, run:

$ npx simple-git-hooks

Add lint-staged.config.js to the project root:

export default {
  '*.{js,ts,jsx,tsx,vue}': ['eslint --fix', 'prettier --write'],
  '*.{json,md,yaml,html}': ['prettier --write'],
  '*.wxml': ['prettier --write', 'stylelint --fix'],
  '*.{css,scss,less,wxss}': ['prettier --write', 'stylelint --fix'],
}

Adjust the globs to match the file types you lint. See lint-staged configuration for more.

Using with Husky and lint-staged

Install dependencies:

$ pnpm add husky lint-staged -D

Add Husky to package.json:

{
  "scripts": {
    "prepare": "husky"
  }
}

Add lint-staged.config.js to the project root (same as above).

Add a pre-commit hook:

$ echo 'pnpm lint-staged' > .husky/pre-commit

For a full-project lint, use pnpm lint or whatever script you define in package.json.

Add a commit-msg hook:

$ echo 'pnpm commitlint --edit "$1"' > .husky/commit-msg

Other

Skipping hooks

Use -n / --no-verify to skip Git hooks:

$ git commit -m "commit message" --no-verify

Use HUSKY=0 to skip Husky:

$ HUSKY=0 git commit -m "commit message"

Use SKIP_SIMPLE_GIT_HOOKS=1 to skip simple-git-hooks:

$ SKIP_SIMPLE_GIT_HOOKS=1 git commit -m "commit message"

To skip hooks for multiple commits in a row, export an environment variable:

$ export HUSKY=0 # Disables all Git hooks

$ git commit -m "first commit"
$ git commit -m "second commit"

$ unset HUSKY # Re-enables hooks

$ git commit -m "third commit"

The same applies to simple-git-hooks.

Troubleshooting: migrating from Husky to simple-git-hooks

See: When migrating from husky git hooks are not running