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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@clonecommand/cli

v0.0.5

Published

CloneCommand Developer Utilities CLI

Downloads

25

Readme

CloneCommand CLI

The CloneCommand CLI (clones) provides developer utilities for managing projects and services in the CloneCommand ecosystem.

Installation

npm install -g @clonecommand/cli

Usage

1. Authentication

Log in to your CloneCommand account:

clones auth login

Check your current status:

clones auth whoami

Log out:

clones auth logout

2. Project Initialization

Initialize a project in the current directory:

clones project init

This will create a ccproject.json file in the current directory.

3. Service Initialization

Initialize a service in a subdirectory (must contain a Dockerfile):

clones service init

This will create a ccservice.json file in the current directory, linking it to your project.

4. Running Commands

Run your application with environment variables automatically injected for the current git branch:

clones run npm run dev

Debugging & Tips

Check Injected Variables

To see exactly which environment variables are being injected into your process, run:

clones run env

This is useful for verifying that secrets and service URLs are correctly resolved for your current branch.

Integration with Scripts

You can make your development workflow seamless by prepending clones run to your scripts in package.json:

"scripts": {
  "dev": "clones run npm run start:dev"
}

This ensures that whenever you run npm run dev, your environment is automatically correctly configured.