env-variables

Managing environment variables across a Next.js monorepo involves using Hermes and Mediapulse env packages to create, update, and validate variables. It enforces best practices by suggesting typed env objects and importing from the appropriate env package rather than reading process.env directly.

To add an environment variable, update the correct env.example file under packages/hermes/env/ or packages/mediapulse/env/. Include a comment explaining the purpose and where to obtain the value, then append env-to-t3 annotations like #required after the value.

Importing from @hermes/env instead of process.env directly ensures type safety and validation. It enforces best practices by suggesting typed env objects, preventing runtime errors from missing or malformed environment variables across your monorepo applications.

To share .env files for local development, use dev-bootstrap.sh to merge env examples and symlink apps to the correct domain. This ensures all applications in the monorepo access shared environment configurations consistently during local development.

Yes, this environment variable approach works with TypeScript monorepos by generating typed env objects using T3 Env and env-to-t3. It provides type-safe environment variable access across your Next.js apps and agents.

The best way to generate env types after updating env.example is to regenerate the typed env object using T3 Env. This ensures your TypeScript types reflect the latest environment variables before importing them from @hermes/env or @mediapulse/env.