One schema, three runtimes — Node.js, Vite, and Next.js each need a different approach to env variable loading.
Your schema is portable. But each runtime loads environment variables differently. CtroEnv adapters bridge the gap — same validation logic, different data sources.
Node.js: process.env + .env Files
The @ctroenv/node adapter loads .env files and wraps process.env:
import { defineEnv, string, number } from "@ctroenv/core"
import { loadEnv } from "@ctroenv/node"
How CtroEnv infers exact types from validators — no z.infer, no manual interfaces, no 50 KB dependency.
A no-fluff comparison of four TypeScript env validation libraries: CtroEnv, Zod, envalid, and t3-env.
Everything you need to know about working with environment variables in TypeScript — from raw process.env to schema validation.
Catch env var problems before they reach production — with objectSource, CtroEnvError, and CI commands.
Most .env setups eventually become operational debt. This guide shows how to build a production-ready Node.js configuration…
Read this and you'll be able to: load the same .env into both a Vite frontend and a Node/Express...
