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

mgre

v1.6.0

Published

Manage Git repository easily

Downloads

4

Readme

mgre

Manage Git repository easily

Why mgre?

When you use git to clone a repository, the repository will be cloned to the current directory if you don't specify a directory. This means that you may need to determine the appropriate directory in which to clone the repository and set up the repository correct username and email to commit. While this may be easy to do once, git clone is often used, and the process can become time-consuming.

To resolve this problem, you can use mgre. With mgre, your directory structure will automatically be organized as follows:

.
├── github.com
│   └── zxf4399
│       └── mgre
└── gitlab.com
    └── zxf4399
        └── mgre

Node.js Compatibility Note: mgre requires Node.js v16+ or higher. Please upgrade your Node.js version if you are using an older version.

Install

# With pnpm
$ pnpm install -g mgre
# With yarn
$ yarn global add mgre
# With npm
$ npm install -g mgre

Config

mgre need a configuration file named config.json to work properly.

mgre will automatically create it in your home directory. For example, on MacOS the path is ~/.mgre/config.json.

Set up codebases

Note: name and email are optional.

{
    "codebases": [
        {
            "email": "[email protected]",
            "name": "zxf4399",
            "url": "github.com"
        }
    ]
}

Usage

Clone a repository

# support clone pattern like git clone
mgre clone https://github.com/zxf4399/mgre.git
# or
mgre clone [email protected]:zxf4399/mgre.git

After cloning, the repository will be moved to the base directory

base
├── config.json
├── github.com
│   └── zxf4399
│       └── mgre
└── mgre.db

Find a repository

# find support fuzzy search
mgre find zxf4399/mgre

If the repository is located, its path will be displayed; otherwise, no output will be generated.

Import existing repositories

If you have an existing repository that you want to import into mgre, you can use the import command.

# For example, if the repository's local path is ~/code/mgre
mgre import ~/code/mgre

After importing, the repository will be moved to the base directory

base
├── config.json
├── github.com
│   └── zxf4399
│       └── mgre
└── mgre.db

If you want to import multiple repositories, you can import them parent directory.

# For example, if the repository A's local path is ~/code/mgre
# and the repository B's local path is ~/code/zxf4399.github.io

mgre import ~/code

After importing, the repositories will be moved to the base directory

base
├── config.json
├── github.com
│   └── zxf4399
│       ├── mgre
│       └── zxf4399.github.io
└── mgre.db

Inspiration

License

MIT