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

@tala-tools/wt

v0.1.0

Published

Git worktree resource synchronization — symlink, copy, or skip local files when creating worktrees

Readme

@tala-tools/wt

Git worktree resource synchronization — symlink, copy, or skip local files when creating worktrees.

The Problem

git worktree add creates a checkout of your tracked files, but a real project won't work without its untracked local state: .env files, node_modules, heavy asset directories, build caches, Python venvs, etc.

wt bridges this gap with a declarative config that describes how each resource should be synchronized into new worktrees.

Install

# As a project dependency
pnpm add -D @tala-tools/wt

# Or run directly
npx @tala-tools/wt status

Quick Start

# 1. Initialize config
wt init

# 2. Edit wt.config.ts to declare your resources

# 3. Create a worktree
wt create feature-auth

# 4. Check everything is synced
wt doctor feature-auth

# 5. See all worktrees
wt status

Configuration

Create a wt.config.ts at your repo root:

import { defineConfig } from '@tala-tools/wt'

export default defineConfig({
    worktreeDir: '.worktrees',
    branchTemplate: 'wt/{name}',

    links: [
        // Secrets — copy into each worktree (one-shot, not live)
        { path: '.env', strategy: 'copy', optional: true },

        // Heavy directories — share via symlink
        { path: 'apps/myapp/out', strategy: 'symlink', createIfMissing: true },
        { path: 'public/assets', strategy: 'symlink' },

        // Dependencies — document but don't sync (run pnpm install instead)
        { path: 'node_modules', strategy: 'skip' },
    ],

    // Named presets for commonly used worktrees
    presets: {
        frontend: { description: 'Frontend development' },
        backend: {
            description: 'Backend work',
            extraLinks: [{ path: '.venv', strategy: 'symlink', optional: true }],
        },
    },

    // Automate post-creation setup
    afterCreate: async ({ worktreePath }) => {
        const { execSync } = await import('node:child_process')
        execSync('pnpm install', { cwd: worktreePath, stdio: 'inherit' })
    },
})

Link Strategies

| Strategy | Behavior | Use For | | --------- | -------------------------------------------- | ----------------------------------- | | symlink | Creates a symbolic link to the main worktree | Large assets, build outputs, caches | | copy | Copies the file/directory (one-shot) | .env, tokens, small config files | | skip | Does nothing (documentation only) | node_modules, .venv (use hooks) |

Commands

wt init

Generate a starter wt.config.ts with commented examples.

wt create <name>

Create a git worktree and sync all configured resources.

wt create feature-auth              # Uses default settings
wt create feature-auth --from main  # Branch from main
wt create feature-auth --force      # Replace existing symlinks

wt sync <name>

Re-apply links to an existing worktree. Run after changing wt.config.ts.

wt doctor <name>

Check that all links are correctly set up. Returns exit code 1 if issues found.

wt status

Show all git worktrees with their sync status and any unmatched presets.

wt remove <name>

Remove a worktree. Use --delete-branch to also delete the git branch.

wt remove feature-auth --delete-branch

Link Options

{
    // Required: path relative to worktree root
    path: 'apps/myapp/out',

    // Optional: source path (defaults to path)
    source: 'apps/myapp/out',

    // Strategy: 'symlink' (default) | 'copy' | 'skip'
    strategy: 'symlink',

    // Don't fail if source doesn't exist
    optional: true,

    // Create the source directory if missing (symlink only)
    createIfMissing: true,
}

Safety

  • Never replaces real files or directories — only symlinks (with --force)
  • Git exclude is automatic — synced paths are excluded from git status
  • Declarative — nothing happens that isn't in your config

Platform Support

| Platform | Status | | -------- | ------------------------------------------------ | | Linux | ✅ Fully supported | | macOS | ✅ Fully supported | | Windows | 🟡 Experimental (uses junctions for directories) |

License

MIT