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

transparent-commitizen

v0.5.2

Published

A stripped-down commitizen adapter that exposes config so that it can be modified and checked into source control

Downloads

2

Readme

GitHub repo size Version License

transparent-commitizen.

A stripped-down, simple commitizen adapter that exposes its logic. This lets you check project-specific configs into source control.

Be a transparent commitizen.

Forked from cz-jira-smart-commit.

Installation

npm i -D transparent-commitizen
npx transparent-commitizen # This command configures tc

You can then edit your commit config by editing .commitconfig/index.js.

If you haven't already installed commitizen itself, you'll need to do so with npm i -g commitizen

Writing your own questions and format

I recommend you look at index.js, which is extremely simple, but here are some instructions anyway.

To add a question, you need ask it by adding to the the array passed to inquirer.prompt, and handle the answer by adding to the function formatAnswers.

Questions in the array passed to inquirer.prompt are a series of objects. Each one should have a type property (type: 'input' is a good place to start), a name for the question, and a message that the user will see as a prompt.

Question objects take a function called validate as an optional property. I've included a helper validate function called exists. If you want to make an answer required you can add validate: validate.exists. You can also look at exists() for the expected input and output of validate functions. If you're curious about input types or validate functions, head over to the inquirer.js docs.

Adding questions to the array of objects makes them available in the answers object. Each answer is a value keyed to the name you gave the question. So, to put to the answers to questions in your commit message, access them by their names in the formatCommit function.

Day to day work

instead of git commit, use git cz:

$ git add .
$ git cz