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

@lcooper/commitlint-config

v2.0.0

Published

Shareable commitlint config for enforcing conventional commits

Downloads

59

Readme

@lcooper/commitlint-config

ci npm license

A sharable commitlint config to enforce conventional commits. Use with @commitlint/cli.

Installation

Install with npm:

npm install --save-dev @commitlint/cli @lcooper/commitlint-config

Install with yarn:

yarn add -D @commitlint/cli @lcooper/commitlint-config

Usage

Add the commitlint field to your package.json file:

"commitlint": {
  "extends": [
    "@lcooper",
  ]
}

Or create a commitlint config file type of your choice in the root folder of your project:

.commitlintrc

{
  "extends": [
    "@lcooper"
  ],
}

.commitlintrc.js

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

Check out the commitlint docs for more details about sharable configs.

Usage with Husky

You can configure a git commit message hook using husky, just add it as a devDependency.

If you are using husky@v9, follow the instructions on commitlints local setup documentation page.

To configure a husky commit message hook with husky@v4, add the following field to your package.json:

"husky": {
  "hooks": {
    "commit-msg": "commitlint -E HUSKY_GIT_PARAMS"
  }
}

Rules

This config extends @commitlint/config-conventional, and defines the following types:

|Type |Title |Description | |----------|------------------------|-------------------------------------------------------------| |build |Builds |Changes that affect the build system or external dependencies| |chore |Chores |Other changes that don't modify src or test files | |ci |Continuous Integration |Changes to continuous integration files and scripts | |docs |Documentation |Changes to documentation | |feat |Features |A new feature | |fix |Bug Fixes |A bug fix | |perf |Performance Improvements|A code change that improves performance | |refactor|Code Refactoring |A code change that neither fixes a bug nor adds a feature | |release |Releases |Changes to prepare for a release | |revert |Reverts |Reverts a previous commit | |style |Styles |Formatting and white-space changes | |test |Tests |Adding missing tests or correcting existing tests |

Additionally, the max line length of commit message headers, bodies and footers is 72 characters to enforce wrapping.

License

MIT