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

@nkzw/define-env

v1.1.0

Published

Type-safe env variables.

Readme

define-env

What is @nkzw/define-env?

process.env.* is not type-safe. It's easy to make a typo, or to forget setting an environment variable in a production environment. @nkzw/define-env is a tiny module that ensures all environment variables are defined on app startup, and provides a type-safe way to access them.

@nkzw/define-env saves time:

  • Type-safe: Auto complete for environment variables. No more typos!
  • Required Variables: All required environment variables must be present, otherwise the app will not start.
  • Immutable environment variables: Environment variables are defined once on app startup, and cannot be changed during runtime.

Installation

npm install @nkzw/define-env

Usage

Create an env.tsx file in the root of your project listing all your env variables:

import defineEnv from '@nkzw/define-env';

export default defineEnv([
  'DISCORD_KEY',
  'PUSH_KEY',
  'STRIPE_SERVER_KEY',
  'WEB_PUSH_PUBLIC_KEY',
  …
]);

Now, your can access your env variables anywhere in your project using env('VARIABLE_NAME'):

import env from './env.tsx';

console.log(env('DISCORD_KEY'));

console.log(env('SUPER_SECRET_KEY')); // Type-error, because `SUPER_SECRET_KEY` is not defined in `env.tsx`.

You can also pass in your own object with environment variables:

export default defineEnv(['APPLE_KEY'], {
  APPLE_KEY: 'AppleBananaKey',
});