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

@zeferinix/commitlint-config

v2.1.1

Published

Shareable commitlint config enforcing conventional commits with a sprinkle of opinions

Downloads

47

Readme

@zeferinix/commitlint-config

Shareable commitlint config enforcing Conventional Commits thru extension of @commitlint/config-conventional. Use with @commitlint/cli.

Installation

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

Usage

Best used with husky as a commit-msg hook.

With a dedicated Commitlint Config

Create a commitlint.config.js file on the root directory and extend with this package:

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

With package.json

In the package.json of your project

{
  "commitlint": {
    "extends": ["@zeferinix"],
    "rules": {}
  }
}

Valid Types

| Type | Description | | --------- | --------------------------------------------------------------------------------------------------------------- | | build | Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm) | | chore | Changes to the build process or auxiliary tools and libraries such as documentation generation | | ci | Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs) | | css | Changes that affect css styling | | docs | Documentation only changes | | feat | A new feature | | fix | A bug fix | | infra | Changes to any infrastructure configuration files and/or scripts (example scopes: aws, heroku, azure, nginx) | | perf | A code change that improves performance | | refactor | A code change that neither fixes a bug nor adds a feature | | revert | Read here | | style | Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) | | test | Adding missing tests or correcting existing tests | | wip | Work in progress. For partial progress that you want to sync on the remote repo. |

Note: Descriptions taken directly from Angular's Commit Message Type Guidelines except for types that are in bold characters as they are new types added by this config.