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

env.d.ts

v0.1.3

Published

Getting tired of looking up how to strongly type environment variables you know will exist just so you can get rid of `string | undefined`? Tired of visiting https://www.totaltypescript.com/how-to-strongly-type-process-env for the thousandth time?

Readme

env.d.ts

Getting tired of looking up how to strongly type environment variables you know will exist just so you can get rid of string | undefined? Tired of visiting https://www.totaltypescript.com/how-to-strongly-type-process-env for the thousandth time?

Run this handy little tool to quickly generate a declaration file for your env vars!

npx env.d.ts

When your .env file looks like this

HELLO=world

You'll get this env.d.ts file

/**
 * This file was autogenerated with "npx env.d.ts"
 * Manual edits are okay, but will be overwritten when you run this command.
 * Be sure to _include_ this file in your tsconfig.json
 */
namespace NodeJS {
  interface ProcessEnv {
    HELLO: string
  }
}

The tool will look for .env and .env.local by default, but you can give it other files

npx env.d.ts .env.development

env.d.ts gets generated in your current working directory, however you can specify an out directory

npx env.d.ts --out-dir src
# or
npx env.d.ts -o src

Disclaimer

This tool doesn't do much and isn't intended to become a replacement for other dotenv tools. It is simply a means to an end when working in a new project. You may want to omit certain environment variables you have in your dotenv files that you know you won't be explicitly using in code, like AWS_PROFILE, or you may want to decorate keys with descriptions of when/how to use them. Use this tool to generate it the first time and clean it up or maintain how you see fit.