Catch env var problems before they reach production — with objectSource, CtroEnvError, and CI commands.
Environment variables are global state. Testing them usually means mutating process.env and hoping you clean up after. CtroEnv gives you better tools.
Testing with objectSource
objectSource() wraps a plain object as an environment source — no globals involved:
import { describe, expect, it } from "vitest"
import { defineEnv, objectSource, string, number } from "@ctroenv/core"
A no-fluff comparison of four TypeScript env validation libraries: CtroEnv, Zod, envalid, and t3-env.
One schema, three runtimes — Node.js, Vite, and Next.js each need a different approach to env variable loading.
How CtroEnv infers exact types from validators — no z.infer, no manual interfaces, no 50 KB dependency.
Configuring environment variables seems simple, but it frequently leads to two common issues in...
The problem When we have a function that interacts with external resources, testing that...
Everything you need to know about working with environment variables in TypeScript — from raw process.env to schema validation.
