env-configuration

Enforce environment variable naming conventions by applying a strict LAT_ prefix to all app variables and validating them at startup. This prevents missing or misnamed configuration across development, CI, and production environments.

The best way to validate environment variables is using parseEnv and parseEnvOptional to read LAT_ prefixed variables with type checks. This fail-fast mechanism catches missing or invalid values during application startup.

Keep your .env.example file up-to-date by enforcing LAT_ prefixed environment variables and using startup configuration validation. This ensures the documentation accurately reflects required variables for local and CI environments.

Yes, parseEnvOptional supports type checking for optional configuration values. Along with parseEnv, it reads LAT_ prefixed environment variables to ensure missing or invalid values trigger a fail-fast response during startup.

Yes, you can use startup validation across local development, deployment checks, and production. Enforcing LAT_ prefixed variables with parseEnv ensures consistent configuration parsing and prevents collisions throughout the deployment lifecycle.

Using a LAT_ prefix for environment variables ensures all app variables follow a consistent naming convention. This practice avoids naming collisions and confusion when managing startup configuration across multiple environments.