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

clone.io

v0.0.0

Published

A tool for cloning resources and their subresources, and operating on them (both the clones and the origins) in a manner similar to git.

Downloads

11

Readme

clone.io

A tool for cloning resources and their subresources, and operating on them (both the clones and the origins) in a manner similar to git.

installing

$ npm install -g clone.io

listing types of resources

$ clone.io list
git
github

viewing the url matchers

$ clone.io github
domain: github.com
matchers:
  user: https://github.com/:username
  repo: https://github.com/:username/:repo

cloning

big resource

This will create a git repository in a directory called substack, download and commit his metadata, and clone all of his repositories into it.

$ clone.io https://github.com/substack

smaller resource

This will clone express, add /issues and /wiki to .git/info/exclude, create an issues repository and use the GitHub API to pull down the issues and commit them as YAML files, and clone the wiki into the wiki directory.

$ clone.io http://github.com/visionmedia/express

getting the rest

Note that when cloning github user account (a big resource), it doesn't pull in as much of each repository (a smaller subresource) as cloning an individual repository does. To get the rest of a repository, after grabbing by cloning the user's account:

$ clone.io http://github.com/substack
$ cd substack/traverse
$ ls -d issues
ls: issues: No such file or directory
$ clone.io pull
$ ls -d issues
issues

updating

You guessed it! It will pull down the default amount of data for the level of resource plus whatever's been pulled down so far.

$ clone pull

status

Not yet implemented. Needs at least one child service implemented first.

todo

  • Make the CLI design a closer match to git
  • Design the CLI to pull down less by default
  • Separate cloning more resources from updating the resources already cloned
  • Keep the services and the commands separate
  • Implement a child service
  • Implement integration

license

MIT.