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

@avelor/bonsai

v0.1.0

Published

Git worktree manager. Branch-centric, zero configuration.

Readme

@avelor/bonsai

Git worktree manager. Branch-centric, zero configuration.

demo

Install

npm install -g @avelor/bonsai
bonsai install

Why

Git worktrees let you work on multiple branches simultaneously in separate directories — no stashing, no context switching. They're one of git's most underused features because the syntax is too hard to remember:

# raw git — you have to know the target path, the branch name, and the right flags
git worktree add ../myrepo-feature-auth feature/auth

# bonsai
bonsai feature/auth

Bonsai fixes that with a branch-centric interface. Just name the branch — bonsai figures out whether to create it, track it from remote, or open an existing worktree. Worktrees always live in .bonsai/ inside your repo.

Setup

Run once after install:

bonsai install
source ~/.zshrc   # or: source ~/.bashrc

This installs a shell function that enables automatic cd when opening worktrees.

Usage

bonsai feature/auth      # open worktree — creates it if needed
bonsai                   # list all worktrees
bonsai rm feature/auth   # remove a worktree
bonsai prune             # remove merged worktrees
bonsai root              # go back to repo root

How worktrees are organized

myrepo/
  .bonsai/
    feature-auth/        ← bonsai feature/auth
    hotfix-login/        ← bonsai hotfix/login
  src/
  package.json

.bonsai/ is added to .gitignore on first use.

Running from inside a worktree

Bonsai detects when you're in a worktree and operates from the repo root automatically:

cd .bonsai/feature-auth
bonsai payments/checkout   # creates .bonsai/payments-checkout from repo root
bonsai rm feature/auth     # removes and cds back to repo root
bonsai root                # cd back to repo root

Requirements

  • git ≥ 2.5
  • Node.js ≥ 18
  • zsh or bash

MIT © Avelor