Publish env schemas from your library so consumers extend them. Build custom validators for domain-specific formats.
Your library needs DATABASE_URL. Another needs JWT_SECRET. Instead of documenting requirements in a README that goes stale, ship them as CtroEnv schemas.
Publishing a Schema from Your Library
defineSchema() is an identity function at runtime — it returns the same object you pass in. At the type level, it preserves exact validator types for composition.
// @myapp/database/src/env.ts
import { defineSchema, string, number, pick } from "@ctroenv/core"
One schema, three runtimes — Node.js, Vite, and Next.js each need a different approach to env variable loading.
A no-fluff comparison of four TypeScript env validation libraries: CtroEnv, Zod, envalid, and t3-env.
How CtroEnv infers exact types from validators — no z.infer, no manual interfaces, no 50 KB dependency.
Introduction In the previous article I described how I split larger TypeScript projects...
Everything you need to know about working with environment variables in TypeScript — from raw process.env to schema validation.
I Built a Browser-Only JSON Schema Validator — Draft-07, $ref, allOf/anyOf/oneOf,...
