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

@magikbee/commitlint-config-magikbee

v1.0.11

Published

This package is used to force the standardisation of commits.

Readme

commitlint config for node projects

This package is used to force the standardisation of commits.

[commitlint][https://commitlint.js.org/#/] - a tool that checks and validates commit messages based on predefined rules. It can ensure that commit messages follow a specific format and style, usually using semantic conventions.

[commitzen][https://github.com/commitizen/cz-cli] - to present an interactive interface to guide the developer in choosing the commit type, scope, description and other information.

The commitlint configuration is based on [conventional commits][https://www.conventionalcommits.org/en/v1.0.0/].

Commitzen is configured to use the same configuration as commitlint via the [@commitlint/cz-commitlint][https://www.npmjs.com/package/@commitlint/cz-commitlint] package. This prevents possible configuration problems.

Installing

  1. In your project folder, run:
npm install --save-dev @magikbee/commitlint-config-magikbee @commitlint/cli@^17.7.1 @commitlint/config-conventional@^17.7.0 @commitlint/cz-commitlint@^17.7.1 commitizen@^4.3.0 husky@^8.0.3 inquirer@^8.2.6
  1. Create (or update) a commitlint.config.js file in your project folder with the following content:
module.exports = {
  extends: ['@magikbee/commitlint-config-magikbee']
};
  1. Add commitizen config to package.json file
"config": {
    "commitizen": {
      "path": "@commitlint/cz-commitlint"
    }
  }
  1. Add script to package.json file to call commit helper
"commit": "git-cz"

Add husky

  1. Install
npm install --save-dev husky@^8.0.3 
  1. Activate hooks
npx husky install
  1. Add hook (to run commitlint and check syntax before adding the commit)
npx husky add .husky/commit-msg  'npx --no -- commitlint --edit ${1}'
  1. Add hook (to use the commit helper when using git commit)

NOTE

It should not be used in conjunction with the standard version package.


npx husky add .husky/prepare-commit-msg "exec < /dev/tty && npx cz --hook || true"
  1. To automatically have Git hooks enabled after install, edit package.json
"scripts": {
    "postinstall": "husky install"
}

Optional - Bump version, generate changelog, create final commit and create a tag

  1. Install standard version
npm i --save-dev standard-version
  1. Add an npm run script to your package.json
{
  "scripts": {
    "release": "standard-version"
  }
}

Now you can use npm run release.

For your first release, simply do npm run release -- --first-release.