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-genius

v1.0.2

Published

Scan project for env usage and create a .env file with detected variables and sensible defaults.

Readme

🌡️ env-genius

env-genius is a beginner-friendly CLI tool that scans your project for environment variables and automatically generates a .env file. Even if your project has no .env, it will detect variables like PORT, MONGO_URI, or any process.env.KEY usage in your code to help you get started quickly.


🚀 Why Use env-genius?

Environment variables are crucial for:

  • Database URLs
  • API keys
  • Secret tokens
  • Port numbers

Beginners often forget to create a .env file or make formatting mistakes. env-genius automatically:

  • Detects environment variables in your code
  • Provides default values if available
  • Creates a .env file for you
  • Gives friendly warnings about formatting issues

🔧 Installation

Local (for your project)

npm install env-genius

Global (CLI accessible anywhere)

npm install -g env-genius

🧪 Usage

1. Scan your project and create .env

npx env-genius
# or if installed globally
env-genius
  • If .env already exists, it will warn you.
  • Use --force to overwrite an existing .env.

2. Dry run (show detected variables without writing)

env-genius --dry

📂 Example

Suppose your project has no .env, and your code contains:

const PORT = process.env.PORT || 3000;
const DB = process.env.DB_URL ?? "mongodb://localhost/test";
const SECRET = process.env.JWT_SECRET;

Running env-genius will generate:

PORT=3000
DB_URL=mongodb://localhost/test
JWT_SECRET=
# TODO: provide value for JWT_SECRET

🛠 How It Works

  1. Scans project files: .js, .ts, .jsx, .tsx, .mjs, .cjs
  2. Detects process.env.KEY usage
  3. Detects fallback/default values if present (|| or numeric defaults)
  4. Generates .env with placeholders for missing values
  5. Provides friendly warnings about key formatting

📄 License

MIT License — free for personal and commercial use.