config-environments

What problem does it solve?

It prevents configuration mistakes that happen when developers encode environment names into variable names or branch on environment at runtime, which can cause wrong credentials, leaks of production-shaped state, and brittle deployments.

Core Features & Use Cases

• Canonical env var naming across environments: Use the same variable name everywhere (e.g., DATABASE_URL) while each environment’s config source supplies the correct value.
• Stops credential selection branching: Avoid logic that picks _DEV/_PROD or _LIVE/_TEST secrets based on NODE_ENV or ENVIRONMENT; isolate credentials at provisioning time instead.
• Fail-fast validation guidance: Treat missing or sensitive configuration as boot-time errors rather than sentinel-defaults that silently point at live systems.
• Review checklist for env-aware code: Evaluate env-var naming, NODE_ENV branching, build-time vs runtime bundling behavior, and scattered env reads.

Quick Start

Review a proposed environment-variable scheme by checking for suffixed variable names and runtime credential selection, then rewrite it to use canonical names loaded per environment.