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 🙏

© 2024 – Pkg Stats / Ryan Hefner

zod-validate-env

v0.0.1

Published

A way to catch missing environment variables, validate their type, and pretty print the validation errors using zod.

Downloads

3

Readme

Credit to packages used in this project

  • zod - https://github.com/colinhacks/zod

Description

A thin wrapper around zod's safeParse which expects a schema that describes the expected env vars and their types, passes process.env into safeParse. On error: pretty prints the validation errors and throws an error. On success: returns a typesafe version of process.env.

Install zod-validate-env

npm install zod-validate-env
yarn add zod-validate-env
pnpm add zod-validate-env

Example usage

// Don't forget to use something like dotenv!
import { z } from 'zod';
import { zodValidateEnv } from 'zod-validate-env';

const schema = z.object({
	NODE_ENV: z.enum(['development', 'production', 'test']),
	DATABASE_URL: z.string().url(),
});

const env = zodValidateEnv({
	schema,
	// Optional, here you could use something like Sentry.
	onError: (message, errors) => {
      // ...  
	},
	// Optional, defaults to console.error.
	log: console.log,
	// Optional, defaults to mapping over errors and using join on the _errors property.
	// safeParse's error.format() is passed in into format.
	format: (errors) => {
        // ...
	},
	// Optional, defaults to '❌ Invalid environment variables:\n'.
	message: 'Failed to validate env vars',
});

// Typesafe version of process.env
console.log(env.NODE_ENV);