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

envtree-sync

v0.4.0

Published

Sync .env files across git worktrees

Downloads

411

Readme

envtree

Sync .env files across git worktrees. Pull env files into branch worktrees, or push changes back.

Install

Add it as a dev dependency in your project:

npm install --save-dev envtree-sync

Or with other package managers:

yarn add --dev envtree-sync
pnpm add --save-dev envtree-sync

Then run it with npx envtree, or add scripts to your package.json:

{
  "scripts": {
    "env:pull": "envtree pull",
    "env:push": "envtree push"
  }
}

Setup

In your repo, run:

npx envtree init

This creates .envtree.json in the repo root with a source directory and glob patterns for your env files. Commit it so all worktrees share the config.

Example .envtree.json:

{
  "source": "~/projects/myapp",
  "files": [
    ".env",
    "apps/*/.env.local"
  ]
}

source is the local directory where your .env files live (e.g. a specific checkout). Supports ~ for the home directory.

Usage

From any worktree:

npx envtree pull            # copy .env files into this worktree
npx envtree push            # copy .env files from this worktree to the source

You can also pass a directory directly, overriding the config source:

npx envtree pull ~/myenvs   # pull from a specific directory
npx envtree push ~/myenvs   # push to a specific directory

Source priority: CLI argument > source in .envtree.json.

Push warns before overwriting files that differ in the target.

Requirements

  • bash, git
  • A git repo with worktrees (git worktree add)