setup-env-validation

You can enforce type-safe environment variable access by setting up a central env.ts file with zod schemas to validate variables. A PostToolUse hook then blocks any direct usage of raw process.env outside this dedicated environment file.

The best way to ban raw process.env usage is implementing a PostToolUse hook that blocks direct access outside a central env definitions file. This ensures all environment variables are validated through a zod schema in your TypeScript project.

Yes, this environment validation approach works specifically with t3-env and zod. It uses a central env.ts file containing zod schemas to validate environment variables and a verification workflow to ensure type safety.

To set up zod schemas for environment validation, install the required packages, create a central env.ts file using the provided template, and wire the PostToolUse hook by placing the validation scripts into your project's hooks directory.

Using a central env.ts file instead of raw process.env ensures centralized type-safe environment management. It validates all environment variables through zod schemas, preventing runtime errors caused by missing or malformed configuration data.

Yes, you can use this hook to validate environment variables in any TypeScript project. It applies to TypeScript projects that want to validate all environment variables and block raw process.env usage through a central env.ts file.