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

pwt-cli

v0.1.2

Published

A CLI for managing Git worktrees.

Readme

PWT - Personal Worktree

A CLI for managing Git worktrees.

Git Worktrees · Zero Config

Installation

# bun
bun install -g pwt-cli

# npm
npm install -g pwt-cli

# pnpm
pnpm add -g pwt-cli

What is PWT?

Git worktrees let you check out multiple branches simultaneously in separate directories. Instead of stashing or committing work-in-progress to switch branches, each branch lives in its own folder.

PWT simplifies worktree management. Create, switch, and clean up worktrees with short commands instead of remembering long Git incantations.

Commands

pwt new <branch>      # Create a new worktree
pwt open <branch>     # Switch to an existing worktree
pwt close             # Close the current worktree
pwt ls                # List all worktrees

Setup

PWT requires a shell wrapper for automatic directory switching. Run the setup command to install it:

$ pwt setup
🔧 Shell wrapper setup for PWT

Install PWT wrapper in ~/.zshrc? [Y/n] Y
✓ Shell wrapper added to ~/.zshrc
  Run 'source ~/.zshrc' to activate

🎉 Setup complete!

The shell wrapper enables automatic cd into new worktrees and automatic dependency installation via ni (if installed).

Manual Shell Wrapper

For manual installation or unsupported shells, add this function to your shell config (~/.zshrc):

# PWT (Personal Worktree) shell wrapper
pwt() {
  PWT_WRAPPER=1 command pwtx "$@" | while IFS= read -r line; do
    if [[ $line == CD:* ]]; then
      cd "${line#CD:}"
    else
      echo "$line"
    fi
  done
}

Example Workflow

Work on multiple features simultaneously without stashing or committing incomplete work. Each worktree is a separate directory with its own branch checked out.

# Quick shorthand - auto-detects new vs open
$ pwt feature/auth
Creating worktree for feature/auth...
✓ Worktree created at ~/code/myproject--feature-auth

# Running again opens existing worktree
$ pwt feature/auth
✓ Now in ~/code/myproject--feature-auth

# List all worktrees
$ pwt ls
┌─────────────────┬────────────────────────────────┬────────┐
│ Branch          │ Path                           │ Status │
├─────────────────┼────────────────────────────────┼────────┤
│ main            │ ~/code/myproject               │ active │
│ feature/auth    │ ~/code/myproject--feature-auth │        │
└─────────────────┴────────────────────────────────┴────────┘

# Switch to another worktree
$ pwt open main
✓ Now in ~/code/myproject

# Clean up when done
$ pwt close
✓ Worktree removed

FAQ

What are Git worktrees?

Git worktrees allow you to have multiple working directories attached to the same repository, each checked out to a different branch. This means you can work on multiple branches simultaneously without stashing or committing incomplete work.

What are the requirements?

PWT requires Git 2.5+ (for worktree support). It works on macOS, Linux, and Windows.

How is this different from git checkout?

With git checkout, you can only have one branch active at a time. With worktrees, each branch lives in its own directory, so you can have multiple branches open in different terminal windows or editors simultaneously.

License

MIT