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

env-shield-pro

v3.0.4

Published

Safe environment variable validation for Node.js

Readme

env-shield-pro

Zero-dependency env variable validation for Node.js (ESM).
Validate, coerce, and fail fast — before production breaks.

npm npm npm version license


Install

npm install env-shield-pro

Quick Start

import { env } from "env-shield-pro";

const PORT = env.PORT.number();                // "3000" → 3000
const SECRET = env.JWT_SECRET.required();       // throws if missing
const NODE_ENV = env.NODE_ENV.enum(["dev", "prod"]);
const IS_ADMIN = env.IS_ADMIN.boolean();        // "true" → true
const DB_URL = env.DATABASE_URL.url();
const EMAIL = env.ADMIN_EMAIL.email();
const TIMEOUT = env.TIMEOUT.default(5000);      // fallback with warning

CLI

npx env-shield-pro check              # validate all env vars are set
npx env-shield-pro check --ci         # exit 0 (pass) / 1 (fail) for CI
npx env-shield-pro scan               # list every env var used in project
npx env-shield-pro generate           # create .env.example from your code

CI Usage (GitHub Actions)

- run: npx env-shield-pro check --ci

Exits 0 if all variables are set, 1 otherwise. Fail your build when config drifts.


API

| Method | Returns | Throws if | |--------|---------|-----------| | .required() | string | missing / empty / null | | .number() | number | not numeric or missing | | .boolean() | boolean | not "true" / "false" | | .enum([...]) | string | not in list or missing | | .default(v) | string \| v | never — warns on fallback | | .url() | string | invalid URL or missing | | .email() | string | invalid email or missing |

Error Colors

❌ Missing required env variable: JWT_SECRET    ← red (fatal)
⚠  TIMEOUT not set, using default: 5000         ← yellow (warning)
import { env, warn, debug } from "env-shield-pro";

Why this?

| | process.env | env-shield-pro | |---|---|---| | Missing vars | undefined silently | ❌ clear error at startup | | Type coercion | manual | .number(), .boolean() | | Validation | manual | .url(), .email(), .enum() | | Defaults | manual | .default() | | CI-ready | ❌ | npx env-shield-pro check --ci | | Size | — | ~2 KB, zero deps |


License

MIT © Karthik