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 🙏

© 2026 – Pkg Stats / Ryan Hefner

minimalcommit

v1.0.2

Published

A minimalist approach toward git commits to keep things simple.

Readme

Minimal Commit

A minimalist approach toward git commit to keep commits simple.

What is Minimal Commit?

Minimal commit is a Node.js based CLI (command line interface) tool that helps you and your team mates to stay consistent with the git commit messages. To commit files using Minimal Commit, you have a list of options to choose from, this list consist type of work you did. This makes things simple and less confusing by choosing an option from a list.

The list of options is limited to only nine types. This is done on purpose to keep the list as short as possible to avoid confusion. The more options you have, the more confusing it will be.

Types

Following are the nine types of commits.

  • ✨ feat to be used for a new feature
  • 🐛 fix to be used for bug fixes
  • 💥 break to be used for breaking changes
  • ♻️ ref to be used for making code/folder refactor
  • 🔖 ver to be used for version changes
  • 📝 docs to be used for documentation
  • 🎨 style to be used for CSS changes
  • 🛠 config for configuration, and dependencies changes
  • 📦 misc to be used for others

Installation

To install Minimal Commit, you can use the following command.

npm install -g minimalcommit

Why Minimal Commit?

  • Straight Forward
  • Easy to read
  • Visually appealing

Usage

mct

Minimal Commit demo

How to write commits?

Here’s the general syntax of Minimal Commit.

<type>: <message>

⚠️ All of the commits must be written in the present tense. Following are some examples:

✨ feat: added sign-up feature ❌
✨ feat: add sign up feature ✅

🛠 config: removed extra extension files ❌
🛠 config: remove extra extension files ✅

The commit title should be precise, and to the point but at the same time, it shouldn't be vague. All of the extra details should go in the description (⚠️ Descriptions are not supported yet.)

✨ feat: add new feature ❌
✨ feat: add sign up feature with forgot password and auth with Google ❌
✨ feat: add sign up feature using OAuth ✅
✨ feat: add sign up feature ✅

Following are some more examples:

🛠 config: add .gitignore file
♻️ ref: move functions to helper.js
📦 misc: add initial test cases
📦 docs: update docs with v2.0 features

Examples

  • You added .yaml file for GitHub Actions

✨ config: add .yaml file for github actions

  • You added some tests cases for the user interface

📦 misc: add test cases for ui

  • You moved some part of the code to components folder

♻️ ref: move pages code into components

  • You updated the code that caused some breaking changes

💥break: update sign-up api endpoints

  • You made some changes to the user interface

🎨 ui: update the auto pages

Support

If you like the work, please give this repo a ⭐️ and feel free to contribute to this project through issues, and pull requests.