Proposal for Config.nonEmptyString() to Handle Empty .env Variables
Config.nonEmptyString("") or Equivalent
Would you be interested in adding a feature like
I've tested this with dotenv, and those variables end up as empty strings. While I know I could validate this myself, I wonder if this use case is common enough to warrant making it a core feature.
Would you be interested in adding a feature like
Config.nonEmptyString("HOST")I've tested this with dotenv, and those variables end up as empty strings. While I know I could validate this myself, I wonder if this use case is common enough to warrant making it a core feature.
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
