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

zeddy-config

v1.0.4

Published

Configuration alternative for NestJS

Readme

Zeddy Config

Zeddy config is a simple configuration library inspired by convict built in TypeScript. It closely follows suggestions written in my upcoming book 'Pragmatic Node.js development: Primer in NestJS'. It also follows the suggestions from The Twelve-Factor App for configuring variables via environment variables.

Usage

In config.ts write your schema. Full interface of options are given in Interfaces section.

import { configz, dotenvize } from "zeddy-config";

dotenvize();

export const config = configz({
  env: {
    description: "Running environment",
    envVar: "NODE_ENV",
    type: "string"
  },
  server: {
    description: "Server info",
    type: "object",
    properties: {
      port: {
        description: "Server port",
        envVar: "SERVER_PORT",
        type: "int",
        validator: (port) => {
          return port === 3000;
        }
      },
      host: {
        description: "Server host",
        envVar: "SERVER_HOST",
        type: "string"
      },
    }
  }
});

// resulting config interface is {env: string; server: {port: number; host: string}}

If you want to use .env files with overrides per NODE_ENV environment variable you can call dotenvize() before configz() to load all necessary environment variables from .env file and .env.${process.env.NODE_ENV}files.

Example project

Example project can be found on https://github.com/zveljkovic/zeddy-config-example.

Interfaces

String value interface expects environment variable in any format.

type ZeddyConfigSchemaStringElementInterface = {
  type: "string";
  envVar: string;
  required?: boolean; // default true
  description?: string;
  validator?: ZeddyConfigSchemaValidator;
}

Integer value interface expects environment variable as whole value.

type ZeddyConfigSchemaIntElementInterface = {
  type: "int";
  envVar: string;
  required?: boolean;
  description?: string;
  validator?: ZeddyConfigSchemaValidator;
}

Float value interface expects environment variable as whole or decimal value.

type ZeddyConfigSchemaFloatElementInterface = {
  type: "float";
  envVar: string;
  required?: boolean;
  description?: string;
  validator?: ZeddyConfigSchemaValidator;
}

Boolean value interface expects environment variable as true/false.

type ZeddyConfigSchemaBooleanElementInterface = {
  type: "boolean";
  envVar: string;
  required?: boolean;
  description?: string;
  validator?: ZeddyConfigSchemaValidator;
}

Object value interface serves as a grouping of environment variables.

type ZeddyConfigSchemaObjectElementInterface = {
  type: "object";
  properties: Record<string, ZeddyConfigSchemaElement>;
  description?: string;
 }