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

@victorfaruna/typed-env

v2.0.3

Published

Type-safe environment validation with full TypeScript inference for Node, Bun, and modern runtimes.

Readme

@victorfaruna/typed-env

Type-safe environment variable validation for Node.js, Bun, and modern runtimes. Zero dependencies.

Install

npm install @victorfaruna/typed-env

Usage

import { defineConfig } from "@victorfaruna/typed-env";

const env = defineConfig({
  DATABASE_URL: { type: "url", required: true },
  PORT: { type: "number", default: "3000" },
  DEBUG: { type: "boolean", default: "false" },
  API_KEY: { type: "string", required: true },
});

console.log(env.DATABASE_URL); // URL object
console.log(env.PORT); // 3000
console.log(env.DEBUG); // false
console.log(env.API_KEY); // "sk-abc123..."

Schema Options

Each key in the schema accepts:

| Option | Type | Description | | ---------- | --------- | ----------------------------------------------------------------- | | type | string | Required. One of "string", "number", "boolean", "url" | | required | boolean | Throws if the variable is missing | | default | string | Fallback value if the variable is not set |

Supported Types

| Type | Output | Example Value | | --------- | --------- | ------------------------------- | | string | string | "hello" | | number | number | "3000"3000 | | boolean | boolean | "true"true | | url | URL | "https://example.com"URL |

Error Handling

If any variables fail validation, all errors are collected and thrown at once:

Error: DATABASE_URL is required but missing
PORT Value must be a number

Runtime Support

This package reads from process.env and has zero dependencies — bring your own env loader.

| Runtime | Setup | | ---------- | ----------------------------------------------------- | | Node | Use dotenv or node --env-file=.env (v20.6+) | | Bun | Works out of the box — .env is loaded automatically | | Deno | Use --env-file flag or @std/dotenv | | Docker | Env vars injected via docker run -e or Compose |

Node.js example

import "dotenv/config";
import { defineConfig } from "@victorfaruna/typed-env";

const env = defineConfig({ ... });

Bun example

// No extra imports needed — Bun loads .env automatically
import { defineConfig } from "@victorfaruna/typed-env";

const env = defineConfig({ ... });

License

ISC