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

@fimbul-works/zodenv

v1.1.0

Published

A tiny TypeScript utility for parsing and validating environment variables using Zod.

Readme

@fimbul-works/zodenv

A tiny TypeScript utility for parsing and validating environment variables using Zod.

npm version TypeScript

Features

  • 🎯 Type-safe environment validation using Zod schemas
  • 📝 Clear error messages with detailed validation feedback
  • 🚀 Zero configuration - works out of the box with process.env
  • 🔄 Configurable - throw errors, exit the process, or stay silent
  • 🔍 TypeScript first - full type inference from your schemas

Installation

npm install @fimbul-works/zodenv zod picocolors

Quick Start

import { z } from "zod";
import { parseEnv } from "@fimbul-works/zodenv";

const env = parseEnv(
  z.object({
    NODE_ENV: z.enum(["development", "test", "production"]),
    PORT: z.string().default("3000"),
    DEBUG: z.boolean().optional(),
  }),
);

console.log(env.NODE_ENV); // fully typed!
console.log(env.PORT);     // string (default: "3000")

If validation fails, you’ll see a nicely formatted error:

Invalid Environment Configuration:
NODE_ENV: "staging"
  Invalid option: expected one of "development"|"test"|"production"

Options

parseEnv(schema, options?)

| Option | Type | Default | Description | | ------------- | ------------------------ | ------------- | ---------------------------------------------------- | | env | Record<string,unknown> | process.env | Source of variables | | exitOnError | boolean | true | Whether to call process.exit on validation failure | | exitCode | number | 1 | Exit code when exitOnError is true | | colors | boolean | true | Enable/disable colored error output |

Custom Error Handling

If you’d rather throw errors instead of exiting:

const env = parseEnv(schema, { exitOnError: false });

try {
  // ...
} catch (err) {
  console.error("Environment validation failed", err);
}

Using in Tests

You can pass a custom env object for isolation:

const env = parseEnv(
  schema,
  { env: { NODE_ENV: "test", PORT: "4000" }, exitOnError: false }
);

License

MIT License - See LICENSE file for details.


Built with ⚡ by FimbulWorks