effect-config

Use Config and ConfigProvider primitives to decode and validate configuration values into typed Effect data structures. This enforces ConfigError behavior and provider-based parsing, replacing unsafe direct environment variable reads with validated typed config.

Typed configuration primitives decode strings into numbers, booleans, URLs, dates, durations, log levels, and redacted secrets with validation. This prevents brittle configuration code by enforcing schema validation before application use.

Yes, Config.schema with Schema.Struct builds nested, composable configuration shapes for predictable validation. This schema-driven approach decodes structured config from environment variables or objects into typed Effect data structures.

ConfigProvider source flexibility allows loading config from environment variables, plain objects, .env contents, directory trees, or fully custom sources. Provider composition enables testing-friendly parsing from in-memory values instead of process.env.

Parse configuration from a test provider built from in-memory values instead of reading process.env directly. ConfigProvider composition allows injecting mock data sources to enforce ConfigError behavior during test setups.

Direct process.env reads create brittle, unsafe configuration code. Decoding and validating environment and file-based settings into strongly typed values using ConfigProvider enforces ConfigError behavior and provider-based parsing for reliable application startup.