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 🙏

© 2024 – Pkg Stats / Ryan Hefner

typed-configs

v0.1.1

Published

Library for accessing your config variables in a typed manner, with runtime checking and a definition exporter. Supports .yml and enviroment variables.

Downloads

22

Readme

Typed Config

Library for accessing your config variables in a typed manner, with runtime checking and a definition exporter. Supports .yml and enviroment variables.

How to use

  1. In your index.ts of your project, add import "reflect-metadata";

  2. Create a config file like this:

    import { Config, ConfigValue } from "typed-configs";
    
    @Config({ configYmlPath: "configs/test.yml" })
    export class Communicator {
        @ConfigValue({
            name: "GREETING",
            description: "They way you say hi to others",
            required: true,
            recommendedValue: "Hello"
        })
        greeting!: string;
    
        @ConfigValue({
            name: "GOODBYE_MESSAGE",
            description: "The way you say goodbye. Optional.",
            required: false
        })
        goodbye: string = "/me left the chat";
    
        @ConfigValue({
            name: "IDLE_SOUND",
            description: "What do you say when doing nothing?",
            required: false
        })
        idleMessage?: string;
    
        @ConfigValue({
            name: "AGE",
            description: "The driver age. should be greater than 18.",
            required: false,
            validate: (age: number) => age >= 18
        })
        age?: number;
    
        nonConfigProperty = "I don't need a type because I don't matter.";
    }
  3. Use the config class somewhere in your code so the decorators get a chance to register the class and its properties.

    import { Configs } from "typed-configs";
    
    console.log(`User says: ${Configs.get(Communicator).greeting}`);
  4. Export the config definition to an actual file (optional but kinda the goal of this library to support this). The Configs.getConfigsDefinitions() method is to know for sure all the decorators have been processed.

    import * as fs from "fs";
    import { Configs } from "./ConfigManager";
    
    Configs.getConfigsDefinitions().then(definitions => {
        fs.writeFileSync("configDefinitions.json", JSON.stringify(definitions));
    });

Important notes:

  • You're required to explicitly set the type of each field with Typescript. This is the only way we can make sure we know the required type before setting any (default) value. Only string, number and boolean are currently supported.
  • For setting the type of a field, goodbye?: string; is allowed, but goodbye: string | undefined; isn't. reflect-metadata will give the first one type String and the latter Object (which isn't allowed by the library).
  • When having a value that's required but doesn't have a default value (like greeting in our example), you can use an exclamation mark (like greeting!: string;) to make the types still work. The library will prevent your program to start if the value isn't provided.