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

git-commander

v0.0.14

Published

A git tool with an easy terminal interface.

Downloads

35

Readme

git commander

A git tool with an easy terminal interface.

ScreenShot

Features

  • [x] git status
  • [x] git add [files]
  • [x] git reset -- [files]
  • [x] git commit [files]
  • [x] git log
  • [x] git reset
  • [x] git diff file
  • [x] git branch
  • [ ] git merge (handling conflict)
  • [ ] git pull/push

Install & Usage

$ npm install -g git-commander
$ git-commander

Requirements

  • git >= 2.4
  • nodejs >= 0.12
  • blessed >= 0.1.7
  • lodash >= 3.0

Key Configuration

We have two key sets vi and mc preconfigured. The default one is vi.

Using the mc key set

You will need to place a file at ~/.config/git-commander/config.json with the following content:

{
    "keySet": "mc"
}
Redefining keys one by one

You also can redefine keys one by one if you would like. You'll need to extend your ~/.config/git-commander/config.json file with a key called keys and put all your key definitions there. For example if you would like to use the mc key set and make key x quit the application, you'll need to add the following:

{
    "keySet": "mc",
    "keys": {
        "common": {
            "quit": [
                "x"
            ]
        }
    }
}

You can find default settings here.

Troubleshootings

ANSI color codes are displayed

ANSI color codes are being displayed if you set "always" for color settings in your .gitconfig. For fixing this, set "auto" for color settings like below.

[color]
    # diff = always
    diff = auto
    status = auto
    ui = auto
    branch = auto

Non-ascii character problem

If you use non-ascii character for source files, You need to disable the core.quotepath option using following command:

$ git config --global core.quotepath false

License

MIT