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

rabbit-warren

v1.0.2

Published

You've been debugging for two hours. You're three `console.log`s deep into `node_modules`, you've got a symlinked local build of some lib, and you have twelve uncommitted files scattered everywhere.

Readme

🐇 rabbit-warren

You've been debugging for two hours. You're three console.logs deep into node_modules, you've got a symlinked local build of some lib, and you have twelve uncommitted files scattered everywhere.

Now something urgent just landed on a different branch.

rabbit-warren saves your whole mess — git changes, untracked files, branch, hand-patched node_modules, symlinked local packages — and gets you out cleanly. Pop back in when you're done.


Install

npm install -g rabbit-warren

Or link locally during development:

npm link

Usage

wrn stash [name]       # save context, clean working directory
wrn pop [name]         # restore most recent (or named) stash
wrn swap <name>        # bidirectional swap — run again to swap back
wrn list               # see all stashes for this repo

wrn enter <name>       # start or resume a named session (restores all repos)
wrn leave              # snapshot all session repos and exit
wrn checkout <branch>  # git checkout, but snapshots into the session first
wrn link [package]     # npm link, but snapshots into the session after

Stash flow

# deep in a debug session on feature/auth — changes everywhere
wrn stash && npm i

# working directory is now clean — switch branches safely
git checkout main

# pick up exactly where you left off - returns to feature/auth
wrn pop

Session flow

Sessions let you name a working context that spans multiple repos. Enter a session, work across repos using the session-aware commands, then leave. Everything is snapshotted together and restored when you come back.

# start a cross-repo session
wrn enter auth-refactor

# work in your API repo — checkout snapshots current state first
cd ~/dev/api
wrn checkout feature/auth-v2

# link and snapshot the frontend repo
cd ~/dev/frontend
wrn link ../api

# urgent fix needed — snapshot all session repos and step out
wrn leave
#   ↓ Leaving session auth-refactor
#     api    feature/auth-v2
#     frontend  main

# later, restore everything exactly as you left it
wrn enter auth-refactor
#   ↑ Restoring session auth-refactor
#     api    feature/auth-v2  (switched)
#     frontend  main

What gets stashed

| Thing | How | | -------------------------------- | ---------------------------------------- | | Tracked file changes | git diff HEAD patch | | Untracked files | copied and removed from working dir | | Symlinked packages | symlink targets saved as JSON | | Hand-edited node_modules files | individual files copied (no full copies) |

Stashes live at ~/.rabbit-warren/<repo>/ — outside the repo, safe from git.

Sessions are stored at ~/.rabbit-warren/sessions/<name>/ — one subdirectory per linked repo, plus a session.json index.


Notes

  • stash always leaves the working directory clean (git status shows nothing)
  • swap is fully reversible — run rabbit-warren swap <name> again to undo
  • Modified node_modules detection uses file mtimes relative to your lockfile
  • Gitignored files (including node_modules itself) stay put after stash