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

env-validate-sarcastically

v1.0.5

Published

Because forgetting .env variables is basically your hobby.

Readme

env-validate-sarcastically 🛠️💀

Because forgetting .env variables is your full-time job.


What is this?

Oh, just another life-saving tool you never knew you needed—until your app blew up because you forgot to set DATABASE_URL. env-validate-sarcastically does one thing: it checks if your .env file has all the required variables from .env.example and screams at you if it doesn’t.

Yes, that's right. It spoon-feeds you the information your own brain refuses to retain.


Installation

Because I know you're just gonna forget this too:

npm install env-validate-sarcastically

Usage

1. Create a .env.example file (because planning ahead is hard)

Put all the required environment variables in it:

PORT=3000
DATABASE_URL=your_database_url
JWT_SECRET=your_secret_key

2. Forget to set some variables in .env (because of course you will)

PORT=3000
DATABASE_URL=your_database_url
# Oops, forgot JWT_SECRET. Enjoy debugging!

3. 3. Run the script and get shamed:

const validateEnv = require("env-validate-sarcastically");
validateEnv();
  1. Behold the judgmental error message:
❌ Missing required environment variables: JWT_SECRET  

There. Now you have no excuses.


Why should you care?

  • Because debugging "why is my app broken?" at 3 AM isn't fun.
  • Because production crashes due to missing .env variables are not a flex.
  • Because telling your boss, "I forgot to set JWT_SECRET" will get you roasted in standup.

Contribute? Sure, why not.

If you somehow find a way to make this even more idiot-proof, feel free to submit a PR. Or just star the repo and pretend you helped.


License

MIT. Do whatever you want, but if you blame me when your app crashes, I will laugh at you.