Package Exports
- config-master
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 (config-master) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
config-master
A convention for storing and retrieving application config. You supply a string (e.g. 'example-app'), the libary will walk up the directory tree merging config stored for this app. The following locations are searched, with the latter taking precedence:
- Any package.json, beneath the
example-appproperty. - Any
.example-app.jsonfiles (or a custom filename you specify).
loadConfig(configName, [options]) ⇒ Object ⏏
Kind: Exported function
| Param | Type | Description |
|---|---|---|
| configName | string |
config name |
| [options] | object |
options |
| [options.startFrom] | string |
directory to begin looking for config |
| [options.filename] | string |
config filename (defaults to .${configName}.json) |
© 2014-17 Lloyd Brookes 75pound@gmail.com. Documented by jsdoc-to-markdown.