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

dgc

v1.1.23

Published

## What It Does?

Downloads

4

Readme

Do Git Commit

What It Does?

it generates commit commands\messages and copy them to your clipboard

How Do I Use It?

run npx dgc and follow the walkthrough

Flags

  • --overrideConfig=./path/to/config will override any config and will load the config in the path instead

  • --autoscope | -a skip scope prompt and uses the current working dir as scope

  • --messageOnly | -m* will strip the commit command and format only it message

  • --execute | -e* will run

    1. git add .
    2. git commit {generated_message}
    3. git pull --rebase
    4. git push
  • --f | -selectFiles on execute will enable to select files from git diff instead of running git add .

flags with * will override each other (only one may be used)

Additional GIT Flags

you can also add any valid git flag to your generated commit like this: npx dgc n --execute it will add -n flag to the generated commit message

Add Custom Config

you can extend the commit generator by having a commit-generator.config.js anywhere above your CWD hierarchy. the config file should export an array of objects as following:

  • the config file can export async function as well, where the first argument is the default steps and the second is the given flags
{
  "prompts": [
    {
      "type": "text",
      "name": "keyA"
    },
    {
      "type": "text",
      "name": "keyB"
      // see prompts docs for further config
    }
  ],
  "format": "{{keyA}} {{keyB}}"
}

prompts - prompts flow to build a single git -m statement. see prompts docs for possible config & usage.

format<string | function> - the fashion in which the input acquired by the prompts flow will be arranged. when value is string the name of each prompt can be used as value by wrapping with double brackets. example: {{prompt_name}} -> user input for that prompt step. when value is function the first argument will be an object with keys & values populated from prompts, the returned value should be a string of the formatted message section