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

dotenv-type-generator

v1.0.0

Published

Reads .env files and auto-generates TypeScript ProcessEnv type declarations

Readme

dotenv-type-generator

Reads a .env file and auto-generates TypeScript ProcessEnv type declarations — zero config, zero annotations required.

Install

npm install -D dotenv-type-generator

Usage

# Generate env.d.ts from .env (default)
npx dotenv-type-generator

# Custom .env path
npx dotenv-type-generator .env.local

# Write to a custom output file
npx dotenv-type-generator .env --out src/types/env.d.ts

# Generate a Zod validation schema instead
npx dotenv-type-generator .env --zod --out src/env.ts

# Print to stdout
npx dotenv-type-generator .env --print

What it generates

Given a .env file:

# Database configuration
DATABASE_URL=postgresql://user:pass@localhost:5432/mydb
PORT=3000
JWT_SECRET=super-secret-key
[email protected]

It generates env.d.ts:

// Auto-generated by dotenv-type-generator. Do not edit manually.

declare namespace NodeJS {
  interface ProcessEnv {
    /** Database configuration */
    DATABASE_URL: string;
    PORT: string;
    JWT_SECRET: string;
    SUPPORT_EMAIL: string;
  }
}

Now process.env.DATABASE_URL is fully typed. Typos in variable names are caught at compile time.

Zod schema output

With --zod, generates a Zod validation schema that validates env vars at startup:

import { z } from 'zod';

export const envSchema = z.object({
  DATABASE_URL: z.string().url(),
  PORT: z.string(),
  JWT_SECRET: z.string(),
  SUPPORT_EMAIL: z.string().email(),
});

export type Env = z.infer<typeof envSchema>;

Auto-run on install

Add to your package.json to auto-generate on every install:

{
  "scripts": {
    "postinstall": "dotenv-type-generator"
  }
}

Use as a library

import { parseEnvFile, generateDeclaration, generateZodSchema } from 'dotenv-type-generator';
import { readFileSync } from 'fs';

const content = readFileSync('.env', 'utf8');
const entries = parseEnvFile(content);
const declaration = generateDeclaration(entries);

Options

| Flag | Description | |------|-------------| | --out <file> | Output file path | | --zod | Generate Zod schema instead of .d.ts | | --print | Print to stdout |