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

handoffdev

v0.1.1

Published

Mirror the current folder into a disposable testing copy.

Readme

HandoffDev

HandoffDev copies the folder you are currently in into another folder for testing.

It is built for workflows like Chrome extension development:

  1. Load one stable unpacked extension folder in Chrome.
  2. Keep working in whatever branch, worktree, or clone you want.
  3. Run handoffdev to refresh the testing copy.
  4. Reload the extension in Chrome.

Install

From npm, after the package is published:

npm install -g handoffdev

From this repo right now:

npm install
npm link

After npm link, handoffdev is available in your shell.

Quick Start

Run it from inside the folder you want to mirror:

cd /path/to/your/project
handoffdev

If you already know the destination:

handoffdev ~/Documents/GitHub/"test dev"
handoffdev "~/Documents/GitHub/test dev"
handoffdev $HOME/Documents/GitHub/"test dev"
handoffdev "$HOME/Documents/GitHub/test dev"
handoffdev --clean ~/Documents/GitHub/"test dev"

Main Commands

handoffdev
handoffdev <destination>
handoffdev --clean
handoffdev --clean <destination>
handoffdev <destination> --clean
handoffdev -- <destination>
handoffdev -h
handoffdev --h
handoffdev -help
handoffdev --help

What It Does

  • Copies the contents of your current folder into a destination folder.
  • Uses rsync --delete, so the destination becomes a mirror of your current folder.
  • Always skips .git/ and .DS_Store.
  • --clean also skips common local junk like node_modules/ and cache folders.
  • If the destination already has files in it, HandoffDev asks for confirmation before deleting anything.

Interactive Mode

  • Running handoffdev with no destination opens an interactive prompt.
  • HandoffDev remembers your last 3 unique successful destinations per project.
  • Git worktrees share the same recent history.
  • If there is no history yet, it asks you to enter a path.

History is stored at:

~/Library/Application Support/HandoffDev/history.json

Path Rules

  • ~ and $HOME are supported.
  • Relative paths are resolved from the folder you run HandoffDev in.
  • Empty destinations, /, protected anchor folders, the current source folder, parents of the source folder, and children of the source folder are rejected.
  • On macOS, GitHub and Github are treated as the same path for safety checks and history matching.

$HOME vs $Home

Use $HOME or ~.

Do not use $Home. In zsh, $Home expands before HandoffDev starts, so HandoffDev cannot recover what you meant and the resulting path is rejected as unsafe.

Development

npm test