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

jambar

v0.2.2

Published

A TypeScript library for reading and parsing environment variables with types. Use `getEnv(key, spec)` to read env vars as string, number, boolean, or enum. Throws if a variable is missing and no default is provided.

Readme

Jambar

A TypeScript library for reading and parsing environment variables with types. Use getEnv(key, spec) to read env vars as string, number, boolean, or enum. Throws if a variable is missing and no default is provided.

Installation

npm:

npm install jambar

yarn:

yarn add jambar

Usage

import { getEnv } from 'jambar';

// String (required when no default)
const apiKey = getEnv('API_KEY', { type: 'string' });
const name = getEnv('NAME', { type: 'string', default: 'world' });

// Number
const port = getEnv('PORT', { type: 'number', default: 3000 });

// Boolean (1 / true / yes / on → true, case-insensitive; otherwise false)
const debug = getEnv('DEBUG', { type: 'boolean', default: false });

// Enum (only values in choices are allowed)
const nodeEnv = getEnv('NODE_ENV', {
  type: 'enum',
  choices: ['development', 'production', 'test'] as const,
  default: 'development',
});

Return types are inferred from the spec, so TypeScript gives you correct types.

Supported types

| type | Description | |----------|-------------| | string | Returns the value as-is. Missing or empty uses default if provided, otherwise throws. | | number | Parses with Number(raw). Throws if the result is NaN. | | boolean | 1, true, yes, on (case-insensitive) → true; anything else → false. | | enum | Only values listed in choices are allowed; otherwise throws. |

For any type, if you set default, it is used when the env var is missing or empty. Without default, missing or empty throws Missing required environment variable: <key>.

API

  • getEnv<K, S>(key: K, spec: S): EnvSpecToType<S>
    Reads and parses the environment variable key according to spec. The return type is inferred as EnvSpecToType<S>.

  • Types
    Exports: EnvSpec, EnvSpecString, EnvSpecNumber, EnvSpecBoolean, EnvSpecEnum<T>, EnvSpecToType<S>.

Development

  • Requires Node.js 20 or later.
  • Run yarn test for tests and yarn compile to build.

License

This project is licensed under the Apache License 2.0. See the LICENSE file for the full text.