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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@yaupon/config-manager

v0.0.0-dev

Published

⚙️ Simple, type-safe configuration management for Node.js

Downloads

3

Readme

Configuration Management

// configuration management // Library will allow to define configuration entries like a interface and variables that later on // are built into schema with use of reflection.

Fully type-safe, easy-to-use and flexible configuration management for your application. Compatible with every back-end framework and up to standards with 12-factor app.

It was created as a replacement for Nest.js s***** configuration management which is either safe to be used as allows startup with invalid configuration or lack of it.

  • We do not want to confuse a configuration management with secrets management, this library can be used at fact to provide secrets but overall I'm working on a separate library for that which will be more focused on such, such as async initialization, secrets rotation, etc. For most usecases at back-end usage of this library is good enough, it's based on convict so it's pretty solid.

TODOs

  • [ ] Add support for configuration files
  • [ ] Add support for custom validation
  • [ ] Add support for externalized configuration (ex. Configcat)
  • [ ] Add support for creating individual configuration entries (to be rethinked)

Usage

import {defineSchema, ConfigurationManager} from "@yaupon/config";

// It's recommended to keep your configurations "scoped" for the things
// that they are responsible for. This way you can easily manage them
// and keep them organized.
type DatabaseConfig = {
    host: string;
    port: number;
    user: string;
    password: string;
    database: string;
}

// It's recommended to define one entry-point of your configuration
// this one should contain all the other configurations. This way
// you can easily manage them and keep them organized. Also
// it's easier to pass them around and have static type checking.
export type Configuration = {
    stripeKey: string;
    database: DatabaseConfig;
}

// Beside defining the whole schema in one go, you can acually define
// smaller parts of it and later merge them together at ConfiguratonManager.
const databaseSchema = defineSchema<DatabaseConfig>({
    host: {
        env: 'DB_HOST',
        description: 'Database host',
        required: true,
        default: null
    },
    port: {
        env: 'DB_PORT',
        description: 'Database',
    },
    // Etc...
})

const configManager = new ConfigurationManager<Configuration>({
    stripeKey: {
        env: 'STRIPE_KEY',
        description: 'Stripe API key',
        required: true,
        default: null
    },
    database: databaseSchema
})

// Now you can access your configuration like this
// get("string") is a autocompleted path to a variables you
// have defined in interface and output from get is typed.

const config = configManager.get("database.host") // string

// You can also get the whole configuration object
// However that's not recommended as I've wasted hours
// debugging why I can't have damn dot-props.
const wholeConfiguration = configManager.get()

Resolve priority

  1. Arguments
  2. Environment variables
  3. Configuration file
  4. Defaults
export const STRIPE_KEY = ConfigEntry.create<string>('STRIPE_KEY', 'stripe_key', 'Stripe API key');