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

ccommit

v2.0.2

Published

😜 βž• πŸ‘” 🟰 ccommit Conventional Commit Generator that interprets commit types from gitmoji and conventional

Downloads

257

Readme

😜 βž• πŸ‘” 🟰 ccommit

ccommit is a conventional commit generator that interprets commit types from gitmoji through conventional-commits to propose a bridged gap through multiple formats.

For developers that use gitmoji it is not always possible to do so in every project. However, to keep workflows the same it would be ideal to introduce a configuration that would provide standards to applications while having some modicum of β€œfun.”

This can hook into your release system to create release notes.

πŸ“ Note: This package is ESM

Usage

Local

Install as a devDependencies:

# pnpm
pnpm add ccommit --save-dev

πŸ“ Note: This is my preference as I try to limit globals wherever possible.

Global

# pnpm
pnpm add ccommit --global

πŸ“ Note: For non-node projects this can be helpful, but again, try to limit globals.

Client

Call directly after staging files

# local
pnpm ccommit -c

# global
ccommit -c

πŸ“ Note: Choose local or global

Hook

Add this to your prepare-commit-msg for git:

exec < /dev/tty
# local
pnpm ccommit --hook || true

# global
ccommit --hook || true

πŸ“ Note: Choose local or global

Options

β–² packages [main] pnpm ccommit -h

  Conventional Commit Generator that interprets commit types from gitmoji and conventional

  Usage
    $ ccommit -c

  Flags
    --breaking, -b       πŸ’₯  Breaking Change
    --commit, -c         πŸ’½  Mode: Client
    --dryrun, -n         🎽  Mode: Dry Run
    --emoji, -e          😜  Emoji (default)
    --hook, -u           πŸͺ  Mode: Hook
    --list, -l           πŸ“–  List all types
    --version, -v        πŸ“¦  Print installed version

  Options
    --format             😜  Commit Format: conventional|gitmoji (default)
    --message            πŸ“  Commit Message
    --scope              πŸ”¬  Commit Scope
    --title              πŸ““  Commit Title
    --type               ✨  Commit Type

  Notes
    - Pass any non-format options the following will be required: --title, --type
    - If you do not pass any options the Conventional Commit Generator prompt will run
      - Branch Name detection is enabled to pre-populate Issue Tracker information in prompt

Formats

Gitmoji

  • 😜 gitmoji
  • πŸ§ͺ Examples
    • ✨ (scope) ABC-123 subject
    • πŸ’š (github) subject
    • πŸ› subject

Conventional

  • πŸ‘” conventional
    • a mapping of gitmoji to what could be construed as it’s more in-depth conventional counterparts
    • can pass --noemoji|-xe and turn emojis off within conventional
  • πŸ§ͺ Examples
    • feat(scope): ✨ ABC-123 subject
    • fix-ci(github): πŸ’š subject
    • fix: πŸ› subject

Roadmap

This was meant to sunset @jeromefitz/git-cz as a year-end personal hackathon. This will keep up with gitmoji and ideally some tenets of β€˜best of both worlds’ could make it to gitmoji-cli some day. (There are a few closed issues on β€˜boring’ versions already, and with this using enquirer probably less and less of a chance.)

As a result it is a mash-up of both and I have tried to add references where applicable: