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

nestjs-auto-env-joi

v1.0.3

Published

Auto Joi validation schema generation for .env files in NestJS

Readme

🚀 nestjs-auto-env-joi

Auto Joi validation schema generation for .env files in NestJS projects.
👉 Save time by auto-generating your validation schema from comments in your .env file!


✨ Features

  • ✅ Supports basic types: string, number, boolean, email, date.
  • ✅ Supports enum with allowed values → // enum:admin|user|guest.
  • ✅ Supports optional variables → // optional.
  • ✅ Automatically marks variables as required by default.
  • ✅ Works seamlessly with @nestjs/config's validationSchema.
  • 🛑 If you forget to add a type tag, the server will throw an error at startup and tell you exactly which line to fix!

📦 Installation

npm install nestjs-auto-env-joi
# or
yarn add nestjs-auto-env-joi

🛠️ Usage Example in NestJS

Create a .env file in your project root with type annotations as comments:

// string
DATABASE_URL=postgres://example

// optional
PORT=3000

// enum:admin|user|guest
USER_ROLE=admin

// boolean
DEBUG=true

Then import and use AutoEnvValidation in your AppModule:

import { Module } from '@nestjs/common';
import { ConfigModule } from '@nestjs/config';
import { AutoEnvValidation } from 'nestjs-auto-env-joi';

@Module({
  imports: [
    ConfigModule.forRoot({
      validationSchema: AutoEnvValidation({
        envPath: '.env', // Optional, defaults to '.env'
      }),
    }),
  ],
})
export class AppModule {}

🏷️ Supported Type Tags

| 🏷️ Type Tag | 📝 Description | 🧑‍💻 Example Annotation | |-------------|----------------|------------------------------| | string | Validates as a string (required) | // string | | number | Validates as a number (required) | // number | | boolean | Validates as a boolean (required) | // boolean | | email | Validates as a valid email string (required) | // email | | date | Validates as a valid date (required) | // date | | enum | Validates string in allowed values (required) | // enum:admin\|user\|guest | | optional | Validates as optional | // optional |


⚠️ Important Notes

  • 🚨 Each environment variable must have a type tag comment line starting with // directly above it.
  • 🚨 If you forget a type tag, your NestJS server will not start and will throw an error showing the line number you need to fix.
  • enum tags must include allowed pipe-separated values.
  • All variables are required by default unless marked with // optional.
  • The .env file must exist at the path provided (default .env).

📄 License

MIT


✍️ Author

Yassine Jdidi


❤️ Happy coding with strong env validation!