Packages that read configuration own a validated `env.ts`, in addition to one `env.ts` per app.
The standard gives each app one env.ts as the only file that reads process.env. CentraKit's request-scoped wiring lives in packages (core, core-ai-runtime, supabase-runtime, stripe, email, next-config, foundation), which run inside several apps and the CLI. Threading every key through each app's env.ts would duplicate the schema in four places.
src/env.ts, built with t3-env, and is the only place in that package that reads process.env.env.ts for app-only keys, and never re-declare a key a package owns.turbo.json lists each key in the env of every task that builds an app using the package.Last updated on