Package Exports
- validate-env-vars
- validate-env-vars/dist/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (validate-env-vars) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
validate-env-vars
A lightweight utility for checking the presence and validity of environment variables, as specified by a Zod schema.
validate-env-vars supports Zod v3, v4, and Zod Mini!
Installation
Using npm:
npm install validate-env-vars --save-devUsage Examples
Create an executable JS file to check an .env file against a Zod schema:
#!/usr/bin/env node
import validateEnvVars from 'validate-env-vars';
import { z } from 'zod';
const envSchema = z.object({
NODE_ENV: z.enum(['development', 'production', 'test']),
API_BASE: z.url(),
GITHUB_USERNAME: z.string().min(1),
});
validateEnvVars({ schema: envSchema });Programmatically check an .env.production file against a Zod schema:
import validateEnvVars from 'validate-env-vars';
import { z } from 'zod';
const envSchema = z.object({
NODE_ENV: z.enum(['development', 'production', 'test']),
API_BASE: z.url(),
GITHUB_USERNAME: z.string().min(1),
});
const preflight = () => {
try {
validateEnvVars({ schema: envSchema, envPath: '.env.production' });
// ... other code
} catch (error) {
console.error(error);
// ... other code
}
};Check env vars before Vite startup and build:
- Define a Zod schema in a .ts file at the root of your project
import { z } from 'zod';
const envSchema = z.object({
NODE_ENV: z.enum(['development', 'production', 'test']),
VITE_API_BASE: z.url(),
VITE_GITHUB_USERNAME: z.string().min(1),
});
// make the type of the environment variables available globally
declare global {
type Env = z.infer<typeof envSchema>;
}
export default envSchema;- Import
validateEnvVarsand your schema and add a plugin to your Vite config to callvalidateEnvVarsonbuildStart
import { defineConfig } from 'vitest/config';
import envConfigSchema from './env.config';
import validateEnvVars from 'validate-env-vars';
export default defineConfig({
plugins: [
{
name: 'validate-env-vars',
buildStart: () => validateEnvVars({ schema: envConfigSchema }),
},
// other plugins...
],
// other options...- Enable typehints and intellisense for the environment variables in your
vite-env.d.ts
/// <reference types="vite/client" />
interface ImportMetaEnv extends globalThis.Env {}
interface ImportMeta {
readonly env: ImportMetaEnv;
}- Add your schema configuration file to your tsconfig's
include
Tips:
- If you don't have a
.envfile, you can pass an empty file. This is useful for testing and CI/CD environments, where environment variables may be set programmatically.
Config Options
| Option | Type | Description | Default |
|---|---|---|---|
schema |
EnvObject |
The schema to validate against (must use string-based types) | |
envPath (optional) |
string |
The path to the .env file | |
exitOnError (optional) |
boolean |
Whether to exit the process or throw if validation fails | false |
logVars (optional) |
boolean |
Whether to output successfully parsed variables to the console | true |
Note: The schema must be a z.object() with string-based field types only (string, enum, literal, or compositions like union/optional of these types). Environment variables are always read as strings.
Schema Recipes
Since environment variables are always read as strings, you'll need to validate and transform them appropriately. Here are some common patterns:
const envNonEmptyString = () =>
z
.string()
.min(1, { message: 'Variable cannot be empty' })
.refine((val) => val !== 'undefined', {
message: "Variable cannot equal 'undefined'",
});
// Integer from string
const envInteger = () =>
z.string().regex(/^-?\d+$/, {
message: 'Variable must be a valid integer',
});
// Boolean from string
const envBoolean = () => z.enum(['true', 'false']);
// Comma-separated list
const envList = () =>
z.string().transform((val) => val.split(',').map((s) => s.trim()));