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

genvx

v0.0.0

Published

A simple CLI tool to sync `.env*` files across projects using a private git repository.

Readme

genvx

A simple CLI tool to sync .env* files across projects using a private git repository.

Features

  • 🔄 Bidirectional sync - Push, pull, or sync .env* files
  • ☁️ Private gitstore - Store env files in a private git repository
  • 📁 Organized storage - Files stored by {host}/{owner}/{repo} structure
  • 🚀 Simple - No encryption, just git + file sync
  • 🧹 Clean - Temporary node_modules/.genvx folder is auto-cleaned after operations

Why?

  • Share env files across your machines easily
  • Backup sensitive env files securely in a private repo
  • No need for local .env.*.encrypted files
  • Simpler than encryption-based solutions (just use a private repo!)

Installation

# Install dependencies
bun install

# Link globally for system-wide access
bun link

# Now you can use genvx anywhere
genvx --help

Configuration

Set your gitstore (private repo) URL via one of these methods (priority order):

  1. CLI flag: --gitstore=<url> (highest priority)
  2. Environment variable: export GENVX_STORE=<url>
  3. Project .env.local: GENVX_STORE=<url> (in current directory)
  4. Global config: ~/node_modules/.genvx/.env.local with GENVX_STORE=<url> (lowest priority)

Global Configuration

For convenience, you can set a default gitstore URL globally:

mkdir -p ~/node_modules/.genvx
echo "GENVX_STORE=https://github.com/youruser/envs.git" > ~/node_modules/.genvx/.env.local

This will be used as a fallback for all projects that don't have their own configuration.

Usage

Push env files to gitstore

# Push all .env* files to gitstore
genvx push

# Or use short alias
genvx p

Pull env files from gitstore

# Pull all .env* files from gitstore
genvx pull

Sync bidirectionally

# Sync based on modification times
genvx sync

# Or use short alias
genvx s

The sync command will:

  • Pull files that only exist in gitstore
  • Push files that only exist locally
  • Compare modification times for files that exist in both places
  • Sync the newer version

How it works

Gitstore Structure

Your private gitstore repository will be organized like this:

gitstore-repo/
├── github.com/
│   ├── snomiao/
│   │   ├── project1/
│   │   │   ├── .env.prod.local
│   │   │   └── .env.dev.local
│   │   └── project2/
│   │       └── .env.prod.local
│   └── otheruser/
│       └── project3/
│           └── .env.local
└── gitlab.com/
    └── ...

Workflow

  1. Clone/Pull: genvx clones your gitstore to ./node_modules/.genvx/gitstore (temporary)
  2. Sync Files: Copies .env* files to/from {host}/{owner}/{repo}/ path
  3. Commit/Push: Commits and pushes changes to gitstore
  4. Cleanup: Removes ./node_modules/.genvx directory

Examples

# Configure gitstore via environment variable
export [email protected]:yourusername/my-env-store.git

# Push your env files
genvx push

# On another machine, pull them
genvx pull

# Or just sync (automatically push/pull based on timestamps)
genvx sync

# Use CLI flag to override
genvx [email protected]:company/envs.git sync

Security Notes

  • ⚠️ Use a private repository for your gitstore
  • ⚠️ Never commit .env* files to your project repos
  • ✅ Your env files are stored in node_modules/.genvx/gitstore/{host}/{owner}/{repo}/
  • 🔒 The gitstore should only be accessible to you/your team

File Structure

Local Project

your-project/
├── .env.local          # Gitignored
├── .env.prod.local     # Gitignored
├── .env.dev.local      # Gitignored
└── node_modules/.genvx/             # Temporary, cleaned after operations

Gitstore Repository

envs-repo/
└── github.com/
    └── yourname/
        └── your-project/
            ├── .env.local
            ├── .env.prod.local
            └── .env.dev.local

Commands

genvx push (alias: p)

Push all local .env* files to gitstore

genvx pull

Pull all .env* files from gitstore to local

genvx sync (alias: s)

Sync files bidirectionally based on modification times

Development

Built with:

  • Bun - Fast JavaScript runtime
  • yargs - CLI argument parsing
  • execa - Process execution

License

This project was created using bun init in bun v1.3.6.