JSPM – forst@1.0.2

Package Exports

forst

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (forst) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Radix Trie Hierarchical Configurations

Setup

Add Forst as a dependency

$ npm install --save forst

Create a folder in which your config tree(s) will live

Example

$ mkdir config

Usage

Consider the following config tree directory

/conf/
├── foo
│   └── bar
│       └── baz.json
├── test
│   ├── bar.json
│   └── foo.json -> { "enabled": false }
└── test.json -> { "enabled": true, "name": "foo" }

Getting the base configuration:

const forst = require('forst');

const config = forst('test', './conf');

console.log(config); // { "enabled": true, "name": "foo" }

Getting the nested configuration:

const forst = require('forst');

const config = forst(['test', 'test/foo'], './conf');

console.log(config); // { "enabled": false,  "name": "foo" }

If the config file is not found it will return either the values of the parent configuration if found or an empty object if nothing is found.

index

forst

Parameters

path (string | Array<string>) Config path
basePath string Tree base path

map

forstMap