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

glone

v0.2.0

Published

Do something after you clone a repo!

Downloads

6

Readme

glone

One file long missing post-clone hook utility for git clone.

  • Run script after cloning is completed.
  • Auto install git hooks.

Usage

Create .glone file in your repository.

{
  "install": "install.sh",
  "hooks": {
    "pre-commit" : "./pre-commit.js"
  }
}

Your scripts can be any kind of file as long as have correct shebang in it.

install.sh

#!/bin/bash
echo "I'm running after cloning."

pre-commit.js

#! /usr/bin/env node
console.log('No commit for ya!')
process.exit(1);

Thats it!

Now when you're going to clone repo, just use npx glone instead of git clone.

npx glone <repository> [directory] -- [other git clone arguments]

Repository mandatory but directory and other git clone arguments are optional of course.

or install glone globally and use standalone.

npm i glone -g glone <repository> [directory] -- [other git clone arguments]

Try it with this repo:

npx glone [email protected]:ramesaliyev/glone.git