app-config
app-config copied to clipboard
Easy Configuration Loader with Strict Validation
Allow the user to do `node -r @app-config/register foo.js` where `foo.js` consumes app-config without loading first. Libraries like dotenv do this.
Closes #130 - [x] Provide a better mechanism for "skipping double runs" of the same extension - [x] Bundle the "environment options trio" type - [x] Extension utils for `getEnv`,...
this error message could be more helpful if it specified the additional properties it found 
Meaning specific environments that are _very_ similar to another, with only a few values different - Explore option to `$extends` w/ a different environment than current one - Explore "combined"...
Resolve paths from the git root or package.json root as a convenience.
Currently it throws an error when `.app-config.yml` isn't found, even if a `.app-config.secrets.yml` file exists with all of the required properties
**[Milestone here](https://github.com/launchcodedev/app-config/milestone/3)** Breaking Changes: 1. Remove some default parsing extensions (#106) - `@app-config/v1-compat` - `@app-config/encryption` - `@app-config/git` 2. Review and rename options for parsing extensions where it makes sense -...
For usage in Node.js, it's useful for intellisense. - [x] `@app-config/core` - [ ] `@app-config/config` - [ ] `@app-config/extension-utils` - [ ] `@app-config/node` - [ ] `@app-config/schema` - [ ]...
```yaml propA: $match: $value: 'foobar' foobar: 42 barbaz: 88 ```
ie allow a user to define their own "jsonnet module"