env-config

To centralize environment variables, route all configuration access through dedicated config modules like `apps/server/src/config.ts` and `apps/web/src/config.ts` instead of direct `process.env` calls. This enforces safe consistency and eliminates scattered defaults across your application.

Managing Vite client-side prefixes requires documenting variables with the `VITE_` prefix in your web config module and `.env.example` file. This ensures proper client exposure rules are followed when adding new feature flags or settings.

Loading .env files for local development in Node 20 uses the `--env-file` flag to inject environment variables at runtime. Standardize this operational guidance to ensure consistent dev environment loading across your server and web client.

Avoiding direct `process.env` reads prevents scattered, error-prone configuration access that leads to misconfiguration and inconsistent defaults. Forcing imports from centralized config modules ensures safe consistency across server and client environments.

Configuring raw store drivers in Vite involves adding the driver configuration to the appropriate server or web config module. You must document the new variables in `.env.example` while following the `VITE_` prefix rules for any client-exposed settings.

You need to update `.env.example` files whenever adding or modifying configuration for the server or web client. Document new variables according to whether they are server-only or client-exposed with a `VITE_` prefix to maintain configuration consistency.