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 🙏

© 2025 – Pkg Stats / Ryan Hefner

git-fetcher

v1.0.0-beta-13

Published

Facilitates working with large repos

Downloads

52

Readme

#Usage

iojs fetch.js --help to show help
iojs fetch.js git@github.com:pawlik/repo_with_rich_history /home/work/i_will_work_here

Note

This code is still in a mess phase. I focused on making it usable ASAP, still need to tidy it up and figure out how to design automatic tests

Fetcher

The main goal of this tool is to provide a fast way for cloning big repositories. It's focus is to bring code as soon as possible, so you can continue in build script inside your repo (this is achieved by making so called shallow repo).

The problem with shallow repo is - it's pain in the ass for developers. Only few commits are available in git log (in case of fetcher only one), and git blame gives you wrong answers. So we try to unshallow repo for you.

How is it achieved

There are two scenarios.

1. very first run ever

  • With the very first run it clones shallow repo from URL, then script exits. So you can call command to build your app.
  • before the scripts exits, though, it calls detached process which
    • creates tmp mirror repo
    • unshallows this repo
    • reassigns remotes on just cloned repo, and unshallows it

2. next run

  • your tmp mirror is here, so it just updates it
  • clones your repo from tmp instead url
  • reassigns remotes, so you can push your work to origin (instead of tmp mirror)

What it can do:

  • when there's no tmp repo mirror it'll fetch shallow, repo, then create (also shallow) tmp repo. With --shallow it will then unshallow tmp, and then unshallow fetched app.

todo

See gh issues