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-custom-scope-changelog

v1.0.1

Published

   

Downloads

8

Readme

cz-custom-scope-changelog

   

How to add on your project

yarn add cz-custom-scope-changelog --dev

Note: you do not need to add neither commitizen nor standard-version, everything is already pre-installed.

And add following config to your package.json

"config": {
   "commitizen": {
     "path": "cz-custom-scope-changelog"
   }
 }

 

Use global commitizen-cli or local git-cz package on your npm scripts to start using structured commit messages.

Questions

  • Jira Issue ID(s) (required) - ISSUE-ID
  • Select the type of change that you're committing - COMMIT-TYPE
  • What is the scope of this change - SCOPE
  • Write a short, imperative tense description of the change - SHORT-DESCRIPTION
  • Provide a longer description of the change
  • Are there any breaking changes
    • Describe the breaking changes

Commit Output:

COMMIT-TYPE(SCOPE): ISSUE-ID - SHORT-DESCRIPTION  

Custom Config

Name of config should be custom-changelog.config.js

Example:

module.exports = {
  /*
    "getCustomScope" method receives all answers by { [name]: value, ... } scheme and is used
    for final transformation of SCOPE value 
  */  
  getCustomScope({ modules, page }) {
    return `${modules} ${page}`;
  },
  /*
     "scopeList" property type is array
     In this array we could add different questions   
     For more details on how to add new one you could use inquirer.js library documentation
  */
  "scopeList": [
    {
      "type": "checkbox",
      "name": "modules",
      "message": "Select the modules touched",
      "choices": ["config", "react", "backboneApp"],
      filter: (val) => {
        if(val.length > 2) {
          return "modules(*)"
        }

        return `modules(${val.join(", ")})`;
      }
    },
    {
      "type": "list",
      "name": "page",
      "message": "Select the page touched",
      "choices": ["*", "offer", "search"],
      filter: (val) => {
        return `page(${val})`;
      }
    },
  ]
};