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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@blazzi/commitlint-config

v0.1.2

Published

Blazzi Commitlint config

Downloads

27

Readme

@blazzi/commitlint-config

npm

Introduction

This sharable commitlint configuration package is designed to help maintain a standardized and readable commit history for our projects. It ensures that all commit messages adhere to a defined format, making the version history cleaner and more informative. Currently extends @commitlint/config-conventional and adds some extra rules.

Installation

Install the package as a development dependency:

With pnpm:

pnpm add --save-dev @blazzi/commitlint-config

With yarn:

yarn add --dev @blazzi/commitlint-config

With npm:

npm install --save-dev @blazzi/commitlint-config

Usage

Once installed, configure commitlint to use the @blazzi/commitlint-config package. Create or edit your commitlint config file (commonly commitlint.config.cjs or .commitlintrc.js) as follows:

module.exports = {
  extends: ['@blazzi/commitlint-config'],
};

or you can also omit the commitlint-config part of the name and just use @blazzi as the package name.

module.exports = {
  extends: ['@blazzi'],
};

Commit Message Format

This configuration enforces the following commit message structure:

<type>(<scope>): <subject>
  • Type: Indicates the purpose of the commit (e.g., feat, fix, docs, style, refactor, test, chore).
  • Scope: A context or category for the commit (e.g., login, user-interface). It's optional and should be in lowercase and kebab-case.
  • Subject: A brief description of the change. It should start with a lowercase letter and be concise.

Examples

Valid Commit Messages

  • feat(auth): implement user authentication
  • fix(api): resolve data fetching issue
  • docs(readme): update installation instructions

Invalid Commit Messages

  • Feature: Add new feature (incorrect type format)
  • fix(Login): fix login error (scope should be in lowercase)
  • fix: fix error (subject should not repeat the type)

Contributing

Your contributions are welcome! Please adhere to this commit message convention when submitting pull requests.

License

This project is licensed under the MIT License - see the LICENSE file for details.

© 2024 Mehmetcan YILMAZ