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-packages

v1.0.0

Published

clone packages from one repo to another

Downloads

17

Readme

clone-packages

clone packages from one npm registry to another, optionally recursively.

# in bash:
$ npm install -g clone-packages
$ clone-packages beefy [email protected] --to http://my.registry.us/ --recursive
# ... time passes and your modules are cloned!

or programmatically:

var clone = require('clone-packages')

// grab this package:
clone('[email protected]', 'http://registry.npmjs.org/', 'http://my.reg/', done)

function done(err) {
  // once cloning is complete
}

API

clone(package, sourceRegistry, targetRegistry, options, ready)

package may be an object: {name: "packageName", version: "version"}, or a string: "package", "[email protected]".

sourceRegistry and targetRegistry must be strings representing URLs of the respective target registries.

options is an object allowing the following keys:

  • username used to authenticate in the publish step for the target registry.
  • password used with username to authenticate.
  • recursive clone all dependencies of package
  • internalize move all packages with external dependencies into the target registry.
  • log a function that will be called with every processed package.

ready is a callback that will be called once cloning has completed.

License

MIT