Runtime environment detection and typed env-var parsing.

Typed environment variable parser

Typed .env loader with schema validation.

typed-env can help us better handle environment variables

Typed environment variables

typed-env-cli can help us better handle environment variables

Canonical environment resolver — typed env names, per-env DB/file/secret config, doctor and CLI for hazo apps

penv's load() and the typed env surface. Ships into user apps — keep it light.

Environment dependent computations

Typed .env manager for modern TypeScript projects (Vite, Next.js, etc.)

Typed env validation with Standard Schema validators, built-in parsers, and startup error reports

Simple environment parser with full typescript inferring support

Create a type-safe proxy for accessing environment variables

The Envless runtime for applications. Loads and decrypts your environment at boot, with a typed `env` proxy, a server and client split, and Next.js, Vite and ESLint entrypoints.

`typed-env` adds a layer over [@humanwhocodes/env](https://www.npmjs.com/package/@humanwhocodes/env) that allows you to convert environment variables into various JavaScript types.

Enable the conversion of environment variables into several JavaScript types

Essential NestJS utilities: typed env config, structured request logging, a declarative module builder for TypeORM/Mongoose/BullMQ, a TypeORM dev seeder, an SSE async-generator decorator, and a shutdown guard.

Typed env registry machinery — a generic factory that turns a per-app variable catalog into a Zod runtime schema, startup validators, and a public-only client snapshot. Ships the framework, not the variable list

Typed environment variables made easy 🚀

Returns an array of Typed Array names that are available in the current environment