npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

env-types-validator

v0.1.0

Published

Type-safe environment variable validation. Define schema once, get runtime validation and TypeScript types automatically

Readme

env-types-validator 🔐

Type-safe environment variable validation for Node.js. Define your environment schema once, get both runtime validation and TypeScript types automatically.

Why?

  • 🛡️ Fail Fast - Validate at startup, catch missing variables immediately
  • 📝 Type-Safe - Full TypeScript support without duplication
  • Zero Dependencies - Just ~3KB minified, nothing else needed
  • 🎯 Simple API - One function, clear schema syntax
  • Multiple Types - Support for string, number, boolean, and JSON

Installation

npm install env-types-validator

Quick Start

Basic Usage

import { defineEnv } from 'env-types-validator';

const env = defineEnv({
  DATABASE_URL: 'string',
  PORT: 'number',
  DEBUG: 'boolean?',  // Optional
});

console.log(env.PORT);    // ✅ TypeScript: number
console.log(env.DEBUG);   // ✅ TypeScript: boolean | undefined

Validation Without Throwing

import { validateEnv } from 'env-types-validator';

const result = validateEnv({
  DATABASE_URL: 'string',
  PORT: 'number',
});

if (result.valid) {
  console.log('✅ Valid!', result.values);
} else {
  console.error('❌ Invalid:', result.errors);
}

Custom Error Handler

import { createEnvValidator } from 'env-types-validator';

const env = createEnvValidator(
  {
    API_KEY: 'string',
    PORT: 'number',
  },
  {
    onError: (errors) => {
      errors.forEach((e) => {
        console.error(`❌ ${e.key}: ${e.reason}`);
      });
    },
  }
);

API

defineEnv(schema, options?)

Simple function for basic use cases.

const env = defineEnv({
  DATABASE_URL: 'string',
  PORT: 'number',
  DEBUG: 'boolean?',
});

createEnvValidator(schema, options?)

Advanced function with full control.

const env = createEnvValidator(schema, {
  throwOnError: true,
  env: process.env,
  onError: (errors) => {},
});

validateEnv(schema, env?)

Non-throwing validation.

const result = validateEnv(schema);
result.valid;    // boolean
result.errors;   // ValidationError[]
result.values;   // Parsed values

Supported Types

  • 'string' - Text values
  • 'number' - Numeric values (converts '3000' → 3000)
  • 'boolean' - Booleans (accepts 'true', 'false', '1', '0')
  • 'json' - JSON strings (parses to objects)

Add ? after any type to make it optional:

const env = defineEnv({
  REQUIRED: 'string',
  OPTIONAL: 'string?',
});

Real-World Example

// env.ts
import { defineEnv } from 'env-types-validator';

export const env = defineEnv({
  DATABASE_URL: 'string',
  DATABASE_POOL_SIZE: 'number?',
  NODE_ENV: 'string',
  PORT: 'number',
  JWT_SECRET: 'string',
  DEBUG: 'boolean?',
  CONFIG: 'json?',
});
// app.ts
import { env } from './env';

app.listen(env.PORT, () => {
  console.log(`Server on port ${env.PORT}`);
});

const db = connect(env.DATABASE_URL, {
  poolSize: env.DATABASE_POOL_SIZE ?? 10,
});
DATABASE_URL=postgres://localhost/db
DATABASE_POOL_SIZE=20
NODE_ENV=production
PORT=3000
JWT_SECRET=secret-key
DEBUG=false
CONFIG={"version":"1"}

License

MIT