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-safe-ts

v1.0.3

Published

Type-safe environment variable loader for Node.js.

Readme

env-safe-ts

Type-safe environment variable loader for Node.js.

npm npm license

GitHub stars

Install

npm install env-safe-ts

Usage

import 'dotenv/config';
import { loadEnv } from 'env-safe-ts';

export const env = loadEnv({
  PORT: { type: 'number', required: true },
  SLACK_API_KEY: { type: 'string', required: true },
  TYPE: {
    type: 'enum',
    required: false,
    values: ['development', 'production']
  }
});

Common Pitfalls & Best Practices

1. Missing vs Empty Environment Variables

env-safe-ts treats both missing variables and empty strings ("") as missing values.

This is intentional.

DATABASE_URL=

is considered the same as:

# DATABASE_URL is not defined

2. Not All Services Use All Environment Variables

In large systems, not all features or services are enabled at the same time.

❌ Anti-pattern

loadEnv({
  PAYMENTS_API_KEY: { type: 'string', required: true },
  SEARCH_API_KEY: { type: 'string', required: true },
});

This assumes everything is always enabled.

✅ Recommended patterns

Service-scoped env schemas

// payments/env.ts
export const paymentsEnv = loadEnv({
  PAYMENTS_API_KEY: { type: 'string', required: true },
});

Load envs only when the service or feature is enabled.

3. Keep a Canonical .env.example

env-safe-ts enforces correctness at runtime, while .env.example documents expectations.

4. Important Note: Environment Loading

env-safe-ts does not load .env files. This is intentional.

You must load environment variables before calling loadEnv, for example:

import 'dotenv/config';

Author

Created and maintained by Misbah Afzal
GitHub: https://github.com/misbahafzal

LICENSE

MIT © Misbah Afzal