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

format-commit

v0.2.2

Published

Format and standardize your Git commits

Downloads

22

Readme

format-commit

Easily format and standardize your commits for all your javascript projects using Git.

Installation

$ npm i format-commit --save-dev

Usage

In the scripts part of your package.json file add a new line "commit": "format-commit" and use $ npm run commit to commit your changes with format-commit.

Or install format-commit globally to use directly $ format-commit command .

The first time you use the command within your project, format-commit will ask you some questions to configure your commits and create a configuration file commit-config.json at the root of your project.

If you want to change format-commit configuration without manually editing the json file you can run the command $ format-commit --config.

Configuration

| Property | Description | | :------- | :---------- | | format | Format option for your commit titles. 1 - (type) Name / 2 - (type) name 3 - type: Name / 4 - type: name 5 - type(scope) Name / 6 - type(scope) name 7 - type(scope): Name / 8 - type(scope): name | | types | The different types of commit allowed. Not defined during assisted configuration, default values used: feat / fix / core / test / config / doc | | scopes | Your application's scopes to categorize your commits (only for related formats 5 to 8). Not defined during assisted configuration | | minLength | Minimum size allowed for your commit titles | | maxLength | Maximum size allowed for your commit titles | | changeVersion | "always": All commits must obligatorily involve a change of version (no preliminary request). "only on release branch": All commits on your release/main branch must obligatorily involve a change of version (no preliminary request). "never": Commits do not necessarily lead to a version change whatever the branch, the wizard will always ask. | | releaseBranch | Release/main Git branch of your project. Use if changeVersion is defined on "only on release branch". | | showAllVersionTypes | Show all possible types of version changes in the wizard, or show only the main ones (major / minor / patch / <custom>) | | stageAllChanges | Auto-stage all changes before each commit |