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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@prerak20/envguard

v0.1.0

Published

TypeScript-first environment variable validation library

Downloads

7

Readme

envguard

TypeScript-first environment variable validation with runtime safety and static inference.

Installation

npm install @prerak20/envguard

Why envguard?

  • Runtime validation for production safety
  • Strong static type inference from schema definitions
  • Chainable builder API focused on environment variables
  • Helpful error output (expected, actual, reason)
  • .env.example generation from the same schema
  • ESM + CJS package output
  • Zero external runtime dependencies

Example

import { boolean, defineEnv, enumType, number, string } from "@prerak20/envguard";

const env = defineEnv({
  PORT: number().min(1000).max(9999).default(3000),
  NODE_ENV: enumType(["development", "production"]),
  DATABASE_URL: string().url(),
  ENABLE_LOGS: boolean().default(false)
});

// env.PORT -> number
// env.NODE_ENV -> "development" | "production"
// env.DATABASE_URL -> string
// env.ENABLE_LOGS -> boolean

Comparison vs zod

envguard is intentionally narrower than zod:

  • Optimized for environment variable workflows
  • Smaller API surface for env parsing tasks
  • Built-in .env.example generation
  • No runtime dependencies

Use zod when you need broad JSON/object/domain validation across app boundaries. Use envguard when env validation is the primary concern.

API Docs

defineEnv(schema, source?)

  • schema: object mapping env keys to schema builders
  • source (optional): custom object, defaults to process.env
  • returns parsed + validated object with inferred TypeScript types
  • throws EnvValidationError when validation fails

string()

  • .min(length)
  • .max(length)
  • .regex(pattern)
  • .url()
  • .optional()
  • .default(value)

number()

  • .min(value)
  • .max(value)
  • .integer()
  • .optional()
  • .default(value)

boolean()

  • .optional()
  • .default(value)

enumType(values)

  • accepts a non-empty tuple/list of strings
  • output type is inferred as a union of those string literals
  • .optional()
  • .default(value)

generateExample(schema)

Returns a formatted .env.example string from the provided schema.

Examples

Custom source object

import { defineEnv, number } from "@prerak20/envguard";

const env = defineEnv(
  {
    PORT: number().default(3000)
  },
  {
    PORT: "8080"
  }
);

Error output

envguard validation failed:
1. PORT
   expected: number >= 1000
   actual: 500
   reason: number is below minimum

Generate .env.example

import { boolean, enumType, generateExample, number, string } from "@prerak20/envguard";

const example = generateExample({
  PORT: number().default(3000),
  NODE_ENV: enumType(["development", "production"]),
  DATABASE_URL: string().url(),
  ENABLE_LOGS: boolean().default(false)
});