Genevy is a tool to generate .env file from your source code.

Intro

Features

• Support for multiple usage syntax of process.env
• Support of default values extracting from code.
• Probably fast, did not benchmark.
• Place for your advertisement.

Usage

Most users (me) use npx to run Genevy on the command line like this:

# Run on project
npx genevy "**/*{.js,.cjs,.ts}" -o .env --merge

# Run on file
npx genevy "config/production.js" -o .env.production --merge

Options

The command line utility has several options. You can view the options by running npx genevy --help

Usage: genevy [options] <pattern>

CLI to generate .env file from source code.

Arguments:
  pattern                           pattern

Options:
  -V, --version                     output the version number
  -o, --output <string>             generate output file
  -i, --ignore <list>               ignore patterns (comma separated list) (default: "node_modules, .git, .svn, .hg")
  -m, --merge                       merge result with output file (default: false)
  --ignoreMismatch <list>           ignore patterns when duplicate defaults usage detected (comma separated list) (default: "config/*.*")
  --ignoreMismatchVariables <list>  ignore specific variables when duplicate defaults usage detected (comma separated list) (default: "NODE_ENV")
  --groupPrefixDepth <int>          group variables by prefix depth (default: 2)
  --groupList <list>                group variables by prefixes list (default: "")
  -h, --help                        display help for command

Options that accept array values can be specified with a comma-delimited list.

Example:

# This example group GOOGLE_ & MONGODB_ variables in single sections.
npx genevy "**/*{.js,.cjs,.ts}" -o .env --merge --groupList "GOOGLE, MONGODB"

--merge

This option makes only appends new variables that are not defined in your .env file.