With envarna, every setting value is strongly typed. No more parseInt(process.env.FOO) Instead, you define settings with decorators and envarna handles parsing and coercion automatically.
Envarna enforces validation rules at startup so you know immediately whether your app has all the settings it needs in the right format. You can also declare sensible defaults inline, making it easy to boot a service in development without requiring .env.
In most dotenv-based apps, your config is fragmented across files and buried in conditional logic. Envarna changes that. All environment variables live in clearly defined settings classes, grouped by concern. For example, DatabaseSettings or EmailSettings. This makes configuration discoverable.
Envarna settings are injectable. This makes testing a breeze. You can instantiate a settings object with test values or mock data. No need to mutate process.env. You can even load settings from alternate sources (e.g., secrets managers or scenario-driven test configs) without changing the rest of your application code.
This site and the library are under development.
