Schema-Validated Env with Joi and forRoot
Fail fast at boot by validating environment variables with a Joi schema in ConfigModule.forRoot.
Why Validate Env at Boot?
In enterprise NestJS services, configuration lives in environment variables. A missing DATABASE_URL or a typo like PORT=tree should never reach production traffic.
- Fail fast: crash at startup, not on the first request three hours later.
- Single source of truth: one schema documents every variable your app needs.
- Type safety: coerce strings into numbers and booleans up front.
This lesson wires a Joi schema into ConfigModule.forRoot so the process refuses to boot when the environment is invalid.
The Problem Without Validation
Without validation, NestJS happily starts with bad config. The failure surfaces later, deep inside a service, with a confusing error.
Below, PORT arrives as a string and the math silently breaks. A real app would also dereference undefined secrets at runtime.
// A common silent bug: env vars are always strings
const PORT = process.env.PORT; // "3000" or undefined
// Expecting a number, but string concatenation happens instead
const nextPort = PORT + 1;
console.log('PORT:', PORT);
console.log('nextPort (wrong):', nextPort); // "30001", not 3001
// Missing secret is undefined, not an error
const secret = process.env.JWT_SECRET;
console.log('JWT_SECRET present?', secret !== undefined);All lessons in this course
- Schema-Validated Env with Joi and forRoot
- Namespaced Config with registerAs
- Loading Secrets from HashiCorp Vault and AWS SSM
- Per-Environment Config and Safe Defaults