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

@comparto/git-c

v2.2.0

Published

Conventional git cli.

Downloads

52

Readme

actions version downloads Code Coverage semantic-release code style: prettier

@comparto/git-c

Interactive conventional commits cli, inspired by git-cz with the ability to leverage commitlint configuration, configuration validation, versatile configuration through cosmiconfig and more

Usage

npx @comparto/git-c
$ npm install -g @comparto/git-c
$ git-c COMMAND
running command...
$ git-c (-v|--version|version)
@comparto/git-c/2.2.0 linux-x64 node-v14.15.1
$ git-c --help [COMMAND]
USAGE
  $ git-c COMMAND
...

Command Topics

Configuration

By default git-c comes ready to run out of the box.

This supports cosmiconfig, so you can customize with either a gitc key in your package.json, or just create a .gitcrc.json, .gitcrc.yml, gitc.config.js, etc. in your project directory.

Options

Breaking Change Emoji

feat: 🎸 dope new feature

BREAKING CHANGE: 🧨 breaks stuff
breakingChangeEmoji: '🧨'

Closed Issue Emoji

fix: 🐛 resolved nasty bug

🏁 Closes: #123
closedIssueEmoji: '🏁'

Disable Emoji

Disable all emojis, overrides breakingChangeEmoji, closedIssueEmoji and emoji options

disableEmoji: false

Details

Allows you to further configure cli and git message output based on type. Default emojis follow standards set by gitmoji

details:
  chore:
    description: Other changes that don't modify src or test files
    emoji: '🤖'
  ci:
    description: Changes to CI configuration files and scripts
    emoji: '👷'
  docs:
    description: Add or update documentation.
    emoji: '📝'
  feat:
    description: A new feature
    emoji: '🎸'
  fix:
    description: Fix a bug.
    emoji: '🐛'
  perf:
    description: Improve performance.
    emoji: '⚡️'
  refactor:
    description: Refactor code.
    emoji: '♻️'
  release:
    description: Deploy stuff.
    emoji: '🚀'
  revert:
    description: Revert changes.
    emoji: '⏪'
  style:
    description: Improve structure / format of the code.
    emoji: '🎨'
  test:
    description: Add or update tests.
    emoji: '✅'

Max Message Length

maxMessageLength: 64

Min Message Length

minMessageLength: 3

Questions

Allows you to toggle questions.

questions:
  - type # Select the type of change that you're committing?
  - scope # Select the scope this component affects?
  - subject # Write a short, imperative description of the change?
  - body # Provide a longer description of the change?
  - breaking # List any breaking changes
  - issues # Issues this commit closes, e.g #123

scope question will not be turned if there's no scopes

Scopes

Allows you to provide list of scopes to choose from.

scopes: []

Will not be in effect if scope question is not turned on.

Types

Allows you to provide list of types to choose from. Can be further configured through Details.

types:
  - chore
  - docs
  - feat
  - fix
  - refactor
  - test

Commitlint

Will leverage Commitlint's configuration instead for options:

  • types correlates to rules[type-enum][2]
  • scopes correlates to rules[scope-enum][2]
  • maxMessageLength correlates to rules[header-max-length][2]
  • minMessageLength correlates to rules[header-min-length][2]
useCommitlintConfig: false