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

@omegasoft/typeconf

v0.6.3

Published

A typesafe hierarchical configuration manager for Node.js and the browser.

Downloads

4

Readme

typeconf   Travis Codecov David codebeat badge npm license

TypeConf is a universal, typesafe, hierarchical configuration manager for Node.js and the browser.

Usage

With TypeConf it's easy to retrieve typed configuration values from different sources:

import TypeConf = require('typeconf');

const conf = new TypeConf()
  .withFile('./conf.json');
  .withEnv();

const port: number = conf.getNumber('port');
const secret: string = conf.getString('secret');

Hierarchical configuration

TypeConf supports different storage backends for configuration values:

All versions:

  • withStore(store: object, name?: string) JavaScript object
  • withSupplier(supplier: (key: string) => any, name?: string) Supplier function
  • set(key: string, value: any) Set or override a value

Node.js only:

  • withArgv() Command line arguments (requires minimist)
  • withEnv(prefix?: string) Environment variables
  • withFile(file: string) JSON or YAML files (.yaml files require js-yaml)

Browser only:

  • withDOMNode(id: string, attribute?: string) DOM element with encoded content attribute

Backends are queried for existing values in the reverse order that they were added. For example:

const conf = new TypeConf()
  .withFile('./conf.json');
  .withEnv()
  .withArgv();

const example = conf.get('example');

In this case TypeConf will check for existing values in the following order:

  1. A command line argument --example
  2. An evironment variable EXAMPLE
  3. An configuration file entry "example": ...

Nested object properties

TypeConf can merge and extract nested object properties from environment varibles:

const conf = new TypeConf()
  .withStore({
    example: {
      test: 'test'
    }
  })
  .withEnv();

This example configuration uses a static object store and environment variables. In order to add or override properties on the example object we can do the following:

export EXAMPLE__TEST="override"
export EXAMPLE__OTHER="another property"

By default, TypeConf uses two "underscore" characters (__) as a separator. We can even define completely new objects using this method:

export ANOTHER__A="property a"
export ANOTHER__B__C="property b.c"
const another = conf.getObject('another');
another === { a: 'property a', b: { c: 'property b.c' } };

API documentation

withStore(store: object, name?: string): TypeConf

Use a JavaScript object as a source. Optionally provide a unique name for the store.

withSupplier(supplier: (key: string) => any, name?: string): TypeConf

Use a supplier function as a source. Optionally provide a unique name for the store.

withArgv(parser?: (args: string[]) => { [key: string]: any }): TypeConf

Node.js only. Use command line arguments as a source. Optionally provide a custom argument parser (uses minimist by default).

withEnv(prefix?: string, separator?: string): TypeConf

Node.js only. Use environment variables as a source. If a prefix is configured, it will be prepended to configuration value names during lookup. The default separator for nested object values is __. For example:

export PREFIX_OBJECT__A="a"
export PREFIX_OBJECT__B__BB="bb"
conf.getObject('object') === { a: 'a', b: { bb: 'bb' } };

withFile(file: string): TypeConf

Node.js only. Use a configuration file as a source. JSON and YAML (requires js-yaml) are supported.

withDOMNode(id: string, attribute?: string): TypeConf

Browser only. Use a DOM element as a source. The configuration must be a Base64-encoded JSON string in an attribute of the element (default: content). For example:

<meta id="conf" content="eyJhIjoiYiJ9" />

set(key: string, value: any): TypeConf

Set an override value.

unset(key: string): TypeConf

Delete an override value.

get(name: string): any

Get a raw value.

get<T>(name: string, transform: (x: any) => T): T

Get a value that is transformed by the supplied function.

getString(name: string, fallback?: string): string | undefined

Get an existing value as a string (using JSON.stringify if necessary) or return an optional fallback string. Throws TypeError if fallback is defined but not a string.

getNumber(name: string, fallback?: number): number | undefined

Get an existing value as a number (using parseFloat if necessary) or return an optional fallback number. Throws TypeError if an existing value cannot be interpreted as a number or if fallback is defined but not a number.

getBoolean(name: string): boolean

Get a value as a boolean. An existing value is always interpreted as true unless it is false or "false". A non-existing value is always interpreted as false.

getObject(name: string, fallback?: object): object | undefined

Get an existing value as an object (using JSON.parse if necessary) or return an optional fallback object. Throws TypeError if an existing value cannot be interpreted as an object or if fallback is defined but not an object.

getType<T>(name: string, Newable: Newable<T>, fallback?: T): T | undefined

Get an existing value as an instance of type T (by passing the raw value as the only argument to the constructor) or return an optional fallback value of the same type. Throws TypeError if an error occurs during the instantiation of type T (constructors should validate the raw configuration value).

toJSON(): object

Aggregate all values from all supported stores as a plain JavaScript object. There are several limitations:

  • Supplier-function stores cannot be aggregated.
  • Environment-variable stores without a defined prefix cannot be aggregated.
  • All command-line arguments are included if the default parser is used.

toBase64(): string

Aggregate all values from all supported stores and encode them as a Base64 JSON string. The same limitations as for toJSON() apply.