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

env-builder-cli

v0.1.0

Published

CLI for env-builder

Readme

env-builder-cli

CLI for env-builder

Installation

npm install -g env-builer-cli

Usage

$ env-builder --help

  Usage: env-builder <source> [options]

  Options:

    -h, --help           output usage information
    -V, --version        output the version number
    -e, --env <env>      name of the env
    -t, --types <types>  comma-separated list of types associated with the app
    -a, --app <app>      name of the app
    -o, --out [out]      write the env to a file (defaut is .env)

  Examples:

    local path
      $ env-builder path/to/config -a my-app
      KEY=VALUE
      OTHER=FOO
      MY_APP_URL=http://myapp.example.com

    pipe to stdout
      $ env-builder path/to/config > .env

    write to .env file
      $ env-builder path/to/config -o

    github repo
      $ GITHUB_TOKEN=my-oauth-token env-builder org/repo

Concepts

Config values are built using inheritance, with last write wins. Say we were setting up my-app locally. It would construct the following inheritance chain:

default (globals - all apps are affected)
local (local globals)
my-app default (defaults across different environments)
my-app local (local specific values)

Apps can also be grouped into types for easy classification. Consider the previous example with added ui and customer-facing types:

default
local
ui default (defaults across all ui apps)
ui local (defaults across all ui local deployments)
customer-facing default (defaults across all customer-facing apps)
customer-facing local (defaults across all customer-facing local deployments)
my-app default
my-app local

The directory structure for the config files might look something like this:

.
├── default
│   ├── default
│   ├── test
│   └── local
├── types
│   ├── ui
│   │   ├── default
│   │   ├── test
│   │   └── local
│   ├── api
│   │   ├── default
│   │   ├── test
│   │   └── local
│   └── auth
│       ├── default
│       ├── test
│       └── local
└── apps
    ├── my-first-app
    │   ├── default
    │   ├── test
    │   └── local
    ├── my-second-app
    │   ├── default
    │   ├── test
    │   └── local
    └── my-third-app
        ├── default
        ├── test
        └── local