Reconciling Config and Context.Tag for Environment Variables
Curious when I'd use Config Vs just Context.Tag with the shape being a map of my env variable?
Currently, I alr have a schema for my env that I'm using to enforce that all the right env are present before building (kinda like the T3 env package)
Feels like there's some duplication with having to define my config too.
Is there a way to reconcile the two?
Currently, I alr have a schema for my env that I'm using to enforce that all the right env are present before building (kinda like the T3 env package)
Feels like there's some duplication with having to define my config too.
Is there a way to reconcile the two?
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
