Nothing solves env loading and validation better than Varlock. Nub v0.7 adds first-party support. If your repo contains an .env.schema file, Nub uses Varlock to load/validate your environment when running a file or script 👇

Zod for env validation is a great pattern, and it's super nice to avoid env.d.ts generation I'm a huge Varlock fan though becuase Varlock solves a bunch of other problems beyond just validation. because it wraps your process, Varlock + .env.schema lets you specify LOADING config in addition to just variable validation. that's why its able to do things like stdio-level redaction, encryption, credential brokering, etc. Zod is just a library so it structurally can't do these things. I'd also argue from an API design standpoint that Varlock's DSL is strictly better than Zod as a mechanism for validation because it's so finely tuned to the kinds of values & validations you commonly need for env vars