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

git-worktree-utils

v1.1.1

Published

Safe git worktree management CLI with environment file syncing

Downloads

2,537

Readme

git-worktree-utils

A safe git worktree management CLI with automatic environment file syncing.

Features

  • Safety checks - Blocks operations with uncommitted changes or unpushed commits
  • Branch protection - Warns if a branch is already checked out elsewhere
  • Main repo protection - Prevents accidental operations on the main repository
  • Automatic .env copying - Copies all .env* files when creating new worktrees
  • Environment syncing - Sync .env files across worktrees with one command
  • Fuzzy search - Find worktrees by partial name match

Installation

npm install -g git-worktree-utils

Usage

Unified CLI

wt <command> [options]

Individual Commands

wt-add [options]
wt-list
wt-find [options]
wt-rename [options]
wt-remove [options]
wt-sync-env [options]

Commands

wt add - Create a new worktree

Creates a new git worktree and automatically copies all .env* files from project directories.

wt add --dirName=my-feature --branchName=feature/my-feature
wt add --dirName=bugfix-123  # uses dirName as branch name

Options:

  • --dirName=<name> - Directory name for the worktree (required)
  • --branchName=<name> - Branch name (defaults to dirName)

wt list (alias: wt ls)

Lists all git worktrees.

wt list

wt find (alias: wt search)

Search worktrees by partial name match (case-insensitive).

wt find --search=feature
wt find --search=FS-1234

wt rename (alias: wt mv)

Rename a worktree directory with safety checks.

wt rename --oldDirName=old-name --newDirName=new-name

Safety checks:

  • Blocks if uncommitted changes exist
  • Blocks if unpushed commits exist
  • Prevents renaming the main repository

wt remove (alias: wt rm)

Remove a worktree with safety checks.

wt remove --dirName=old-feature

Safety checks:

  • Blocks if uncommitted changes exist
  • Blocks if unpushed commits exist
  • Prevents removing the main repository

wt sync-env (alias: wt sync)

Sync .env* files from current worktree to other worktrees.

wt sync-env --to=other-worktree  # sync to specific worktree
wt sync-env --all                 # sync to ALL other worktrees

How .env Copying Works

When creating a worktree or syncing, the tool:

  1. Finds all directories containing package.json or project.json (excluding node_modules)
  2. Copies all .env* files (.env, .env.local, .env.development, etc.) to the same relative path in the target worktree

This is especially useful for monorepos where environment files are scattered across multiple projects.

Examples

Typical Workflow

# Create a new feature worktree
wt add --dirName=my-feature --branchName=feature/awesome

# ... work on the feature, add new .env variables ...

# Sync your .env changes to all other worktrees
wt sync-env --all

# Find a specific worktree
wt find --search=awesome

# Clean up when done
wt remove --dirName=my-feature

Use with npm scripts

Add to your package.json:

{
  "scripts": {
    "wt:add": "wt add",
    "wt:list": "wt list",
    "wt:sync": "wt sync-env --all"
  }
}

License

MIT

Author

Avi Weiss