benedyktdryl/config

JavaScript application configuration: moder, customisable & extensible

config's Issues

Babel providers are not resolving modules correctly

Using any of modules imports inside config file which is parsed by Babel leads to "module not found error" due to different path of parsed file and path of provider.

Fix it by setting cwd or using custom module resolver.

Handlers should be pure functions

No need to make handlers class based. They should have I/O model and be exported as object literal with format + parse method.

Allow postprocessing hooks

Postprocessing hooks should be allowed to be injected along with handlers and providers. Implement basic use cases:

• JOI based validation
• filling with defaults (can be done with JOI but check if it can be done separately)
• replacing %parameter% with passed parameter (Symfony style)

Implement handlers

To cover same file formats as node-config for start we need to implement such providers:

• JSON5 (https://github.com/json5/json5)
• CSON (https://github.com/atom/season)
• TOML (https://github.com/BinaryMuse/toml-node)
• HJSON (https://github.com/hjson/hjson-js)
• XML https://github.com/nashwaan/xml-js

Implement deferred values

Deferred values should be implemented as provider (ProviderDeferred).

Example of usage:

const provider = new ProviderDeferred({
  'path.to.nested.property': config => composedValue
});

This way, we are not polluting configs with deferred methods and also, we can use deferred values even when using non executable formats like JSON or YAML.

Fix inconsistency in environment variables provider

Right now, config for ProviderEnvVariables looks like this:

{
  "ENV_VARIABLE_NAME": "path.to.nested.property"
}

To be consistent with #2 ProviderDeferredValues, it should be implemented like this:

{
  "path.to.nested.property": "ENV_VARIABLE_NAME"
}