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

@themusicdev/env-sync

v0.2.0

Published

Sync a monorepo root .env into per-app .env files declared by .env.example mapping headers

Downloads

335

Readme

@themusicdev/env-sync

CLI that syncs a monorepo root .env into per-app .env files. Each app's .env.example declares its contract: a # .env.mapping header lists which vars to pull from root, the body lists all vars (header + local-only).

Contract

# apps/api/.env.example
# .env.mapping        ← marker: sync list starts
# API_PORT            ← same-name var from root .env (must exist in root)
# PORT=API_PORT       ← rename syntax (rare — framework-mandated names)

API_PORT=             ← header vars get root values on `env-sync write`
LOG_LEVEL=debug       ← body-not-in-header = local-only, never synced

Rules:

  • Header var missing in root .env → hard error (check exits 1, write aborts).
  • Body vars not in header are local-only — left alone.
  • Keys in an app .env not declared in its example are flagged (check) and preserved (write).

Commands

| Command | What it does | |---|---| | env-sync check | Dry-run drift report. Exit 1 on errors. | | env-sync write | Regenerate per-app .env from root + headers, preserving local values and undeclared extras. | | env-sync create | Scaffold root .env + .env.example from the union of all app headers. Skips existing root files. |

Run from the monorepo root. Root files live at ./.env and ./.env.example.

Install

bun add github:TheMusicDev/env-sync   # from GitHub
bun add @themusicdev/env-sync         # from npm (once published)
bun link @themusicdev/env-sync        # local dev, after `bun link` in this dir

Typical root scripts in the consuming repo:

{
    "env:check": "env-sync check",
    "env:sync": "env-sync write"
}

Turbo note

Turbo hashes env files into cache keys — add .env to globalEnv (or task env keys) in turbo.json, or every sync silently poisons cache correctness.

License

MIT — contributions welcome, see CONTRIBUTING.md.