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

commitiquette

v1.2.1

Published

Plugin for commitizen to use commitLint config

Downloads

17,885

Readme

Commitiquette

Plugin for Commitizen that uses commitLint configuration. Allows you to use both Commitizen and commitLint with a single configuration.

Node.js CI codecov npm version

Installation

You will first need to follow the commitizen and commitlint instalation instructions if you do not already have these installed.

Use npm or yarn to install commitiquette into your project.

npm install commitiquette --save-dev

Usage

Update package.json Commitizen configuration.

  "config": {
    "commitizen": {
      "path": "commitiquette"
    }
  },

Purpose

The purpose of this project is to have a single configuration for both commitlint and commitizen -- while prompting the user for each answer.

Similar Projects

Both of these wonderful projects are use the commitlint config as well.

Commitiquette differs by using simple prompts, list selects whenever possible, for answers -- much like the cz-conventional-changelog commitizen plugin.

Fully Configurable

Commitiquitte is fully configurable using the commitlint configuration.

Examples

Disable Prompting for scope

module.exports = {
  extends: ['@commitlint/config-conventional'],
  rules: {
    'scope-empty': [2, 'always']
  }
};

List select for scope

module.exports = {
  extends: ['@commitlint/config-conventional'],
  rules: {
    'scope-enum': [2, 'always', ['docs', 'core', 'lib', 'misc', 'etc']]
  }
};

Filtering and Validation

Commitiquette will validate against all but the deprecated commitlint rules.

NOTE: This is not a replacement for commitlint. Commitlint should still validate the message before each commit.

Where possible, commitlint rules will be used to filter messages.

Validation is run at Level Error (2) -- where filtering will apply at if the rule is set to Warn (1) or Error (2.)

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

License

MIT