Why use Config for Env Configuration instead of T3 Env?
Question:
Something that confuses me is why use Config for Env Configuration
I usually use T3 Env so I'm used to having env defined in one place
With
1. Can be defined / used in multiple places and must search instead of "find all references" of env variable.
2. Doesn't this increase the risk of mistyping / spelling error since it's string?
The only reason I can think of using Config is to recover from env undefined,
but when do we want that instead of just crashing / not starting the app in first place if we have missing env vars?
Something that confuses me is why use Config for Env Configuration
I usually use T3 Env so I'm used to having env defined in one place
With
const host = yield* Config.string("HOST")1. Can be defined / used in multiple places and must search instead of "find all references" of env variable.
2. Doesn't this increase the risk of mistyping / spelling error since it's string?
The only reason I can think of using Config is to recover from env undefined,
but when do we want that instead of just crashing / not starting the app in first place if we have missing env vars?
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
