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

g4c

v1.6.0

Published

A basic pure js git CLI implementation based on isomorphic-git.

Downloads

51

Readme

Commands supported

- g4c clone URL
- g4c clone URL DIRECTORY
- g4c clone # (automatically clones from package.json, or secrets file)
- g4c checkout --force HEAD
- g4c pull
- g4c pull --ff-only
- g4c status
- g4c add --all
- g4c commit -m "My commit message"
- g4c push

TODO:

- git # As an alias, comming soon
- g4c add FILE(s)
- g4c add .
- git pull origin pull/123/head

Setup

  • npm i -D g4c
  • npm i -g g4c -- Global install

Goals

  1. Make common git commands easy to use in JavaScript shells 🚀
    • This includes commands such as git clone, git pull, and git push.
  2. Provide configuration options via config file, package.json and ENV variables ⚙️
    • This will make it easier for developers to customize the behavior of g4c to match their specific needs.
  3. Minimize cold-boot time and overhead in browser environments ⏱️
    • This is important for web IDEs. By minimizing the cold-boot time, developers can maximize cycle time and review PR's more efficiently.
  4. Improve the developer experience (DX) for JS devs as much as possible 👩‍💻
    • Following in the foot steps of vite and git to improve workflows.

Configuration Precedence

  • First, the long form package.json -> repository field is read
  • Then, package.json -> author field is read for email and name
  • Then, package.json -> g4c
  • Finally, SECRETS.g4c.json can veto all others
  • Unless, yoy provided an argument in the command line

All of these are optional:

// SECRETS.g4c.json
{
  "proxy": "https://cors.isomorphic-git.org",
  "useProxyOnBareMetal": false,
  "username": "inu",
  "password": "neko",
  "authorName": "John Doe",
  "authorEmail": "[email protected]",
  "repoUrl": "https://github-sucks.com/user/project.git"
}