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

cz-customizable-te

v6.2.0

Published

Commitizen customizable adapter following the conventional-changelog format.

Downloads

8

Readme

cz-customizable-te

NOTE: Same as cz-customizable, but with the commit tailored to my liking and to jive with waffle.io. It also includes Pivotal commit syntac.

The customizable Commitizen plugin to help achieve consistent commit messages like the AngularJS team.

screenshot

Suitable for large teams working with multiple projects with their own commit scopes. When you specify the scopes in your .cz-config.js, cz-customizable allows you to select the pre-defined scopes. No more spelling mistakes embarrassing you when generating the changelog file.

Steps:

  • install commitizen in case you don't have it: npm install -g commitizen. Make sure you have the latest version of commitizen installed globally.

  • install the cz-customizable: npm install cz-customizable --save-dev

  • configure commitizen to use cz-customizable as plugin. Add those lines to your package.json:

    ...
    "config": {
      "commitizen": {
        "path": "node_modules/cz-customizable"
      }
    }

You have two options to configure cz-customizable:

  • Config block in your package.json:
    ...
    "config": {
      "commitizen": {
        "path": "node_modules/cz-customizable"
      },
      "cz-customizable": {
        "config": "config/path/to/my/config.js"
      }
    }

Note: option one allows you to have your config away from root directory. It also gives you a change to define any name to your cz-config.js.

Notes:

  • you should commit your .cz-config.js file to your git.

From now on, instead of git commit you type git cz and let the tool do the work for you.

Hopefully this will help you to have consistent commit messages and have a fully automated deployemnt without any human intervention.

Use Pivotal Commit Syntax, ie [Finishes #12345689]:

  • Add to your .cz-config.js config:
    module.exports = {
      pivotal: true,
      ...
    }

Options

Here are the options you can set in your .cz-config.js:

  • scopes: {Array of Strings}: Specify the scopes for your particular project. Eg.: for some banking system: ["acccounts", "payments"]. For another travelling application: ["bookings", "search", "profile"]
  • scopeOverrides: {Object where key contains a Array of String}: Use this when you want to override scopes for a specific commit type. Example bellow specify scopes when type is fix:
  scopeOverrides: {
    fix: [
      {name: 'merge'},
      {name: 'style'},
      {name: 'e2eTest'},
      {name: 'unitTest'}
    ]
  }
  • allowCustomScopes: {boolean, default false}: adds the option custom to scope selection so you can still typea scope if you need.
  • allowBreakingChanges: {Array of Strings: default none}. List of commit types you would like to the question breaking change prompted. Eg.: ['feat', 'fix']
  • appendBranchNameToCommitMessage: If you use cz-customizable with cz-customizable-ghooks, you can get the branch name automatically appended to the commit message. This is done by a commit hook on cz-customizable-ghooks. This option has been added on cz-customizable-ghooks, v1.3.0. Default value is true.

Related tools:

  • (https://github.com/commitizen/cz-cli)
  • (https://github.com/stevemao/conventional-recommended-bump)
  • (https://github.com/semantic-release/semantic-release)
  • (https://github.com/uglow/cz-customizable-ghooks)

GOTCHAS

  • backticks If you wish to have backticks in your content, for example "feat: `string`", the commit preview will be "feat: \\string\\\\". Don't worry because on your git log will be "feat: `string`" as desired.

  • multiline contents on the body of the message Body is the only place where you can use a pipe to break lines. E.g.: you type this: my items are:| - item01| - item 02, which will become:

my items are:
 - item01
 - item 02

CONTRIBUTING

Please refer to:

Leonardo Correa