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

easyenvguard

v2.0.0

Published

Developers often forget to define required environment variables (.env files). This package will automatically validates required environment variables on startup (Now supports TS).

Readme

EasyEnvGuard - Environment Variable Validator

📌 Introduction

EasyEnvGuard is a lightweight and easy-to-use environment variable validator for Node.js applications. It ensures that required environment variables are defined and have the correct data types, preventing runtime errors due to missing or incorrectly formatted variables.

Built with simplicity and reliability in mind, EasyEnvGuard is an essential tool for developers looking to enhance the robustness of their applications.

🚀 Features

  • ✅ Ensures required environment variables are present.
  • ✅ Validates data types (string, number, boolean).
  • ✅ Supports both CommonJS (require) and ES Modules (import).
  • ✅ Improves application reliability and maintainability.
  • ✅ Lightweight, fast, and dependency-free.
  • ✅ Easy integration with .env files.

📦 Installation

Install EasyEnvGuard using npm:

npm install easyenvguard

Or with yarn:

yarn add easyenvguard

🔧 Usage

1️⃣ Create a .env file (if using dotenv)

PORT=3000
DATABASE_URL=mongodb://localhost:27017
JWT_SECRET=mysecret
DEBUG_MODE=true

2️⃣ Use easyenvguard in your Node.js project

For CommonJS (require) Users

require("dotenv").config(); // Load .env file
const { validateEnv } = require("easyenvguard");

validateEnv({
  PORT: "number",
  DATABASE_URL: "string",
  JWT_SECRET: "string",
  DEBUG_MODE: "boolean",
});

console.log("✅ All required environment variables are valid!");

For ES Module (import) Users

import "dotenv/config"; // Load .env file
import { validateEnv } from "easyenvguard";

validateEnv({
  PORT: "number",
  DATABASE_URL: "string",
  JWT_SECRET: "string",
  DEBUG_MODE: "boolean",
});

console.log("✅ All required environment variables are valid!");

✅ Validation Rules

| Expected Type | Accepted Values Example | | ------------- | ------------------------------ | | string | Any text ("example") | | number | Numeric values (3000, 42) | | boolean | true or false (as strings) |

⚠️ Error Handling

If an environment variable is missing or has the wrong type, EasyEnvGuard will throw an error:

EnvGuardError: Missing required environment variable: JWT_SECRET
EnvGuardError: Invalid type for PORT. Expected number, but got string.

📖 Best Practices

  • Use .env.example files: Maintain a template of required environment variables for better collaboration.
  • Validate environment variables at application startup to catch issues early.
  • Use dotenv or environment managers to manage environment variables across different stages (development, staging, production).

🛠️ Compatibility & Support

| Node.js Version | Support | |----------------|---------| | 18.x+ | ✅ Fully Supported | | 16.x | ✅ Fully Supported | | 14.x | ⚠️ Limited Support (End-of-Life soon) | | < 14.x | ❌ Not Supported |

📜 License

MIT License. Feel free to use and contribute!

🤝 Contributing

Contributions are welcome! If you have ideas for improvements, submit an issue or a PR.

How to Contribute

  1. Fork the repository.
  2. Create a new branch (feature-branch).
  3. Make your changes and commit (git commit -m "Added a new feature").
  4. Push to your fork and submit a pull request.

🛠️ Roadmap

  • [ ] Add TypeScript support
  • [ ] Provide built-in support for custom validation functions
  • [ ] Improve error logging and debugging experience

Star this repo if you find it useful! 🚀

🔗 GitHub Repository