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

@dinakars777/env-doctor

v1.0.0

Published

A beautiful, interactive CLI to validate local .env files against .env.example templates.

Readme

env-doctor 🩺

A beautiful, interactive CLI to diagnose and fix missing local environment variables.

env-doctor screenshot (Imagine a beautiful clack-based terminal here)

The Problem

Every developer has pulled down a project, run npm run dev, and watched it crash because they are missing a variable in their .env file that another developer added, but forgot to tell them about.

env-doctor prevents "it works on my machine" syndrome by validating your local .env file against your team's .env.example template and interactively prompting you to fill in missing values.

Features

  • Zero configuration required. Just run the command in your project root.
  • 🎨 Beautiful UI. Powered by @clack/prompts and picocolors.
  • Extremely fast. Minimal dependencies.
  • 🛡️ Non-destructive. Appends new keys without touching your existing ones.

Usage

Simply run this command in the root of your project:

npx @dinakars777/env-doctor

Or install it globally:

npm install -g @dinakars777/env-doctor
env-doctor

How It Works

  1. It searches for .env and .env.example in your current directory.
  2. It lists any keys present in .env.example that are missing or empty in your .env.
  3. It launches an interactive prompt asking you for the missing values.
  4. It safely appends them to your local .env and you're ready to code!

Customization

You can specify custom paths for your environment files:

npx @dinakars777/env-doctor --example .env.template --env .env.local

Contributing

Pull requests are welcome!

git clone https://github.com/your-username/env-doctor.git
cd env-doctor
npm install
npm run dev

License

MIT