Convict

Convict expands on the standard pattern of configuring node.js applications in a way that is more robust and accessible to collaborators, who may have less interest in digging through code in order to inspect or modify settings. By introducing a configuration schema, convict gives project collaborators more context on each setting and enables validation and early failures for when configuration goes wrong.

Features

• Loading and merging: configurations are loaded from disk or inline and merged
• Nested structure: keys and values can be organized in a tree structure
• Environmental variables: values can be derived from environmental variables
• Command-line arguments: values can also be derived from command-line arguments
• Validation: configurations are validated against your schema (presence checking, type checking, custom checking), generating an error report with all errors that are found
• Comments allowed: schema and configuration files can be either in the JSON format or in the newer JSON5 format, so comments are welcome
• Configuration file additional types support: custom file type support can be used for the configuration file

Install

1npm install convict

Usage

An example config.js file:

1var convict = require('convict');
2
3convict.addFormat(require('convict-format-with-validator').ipaddress);
4
5// Define a schema
6var config = convict({
7  env: {
8    doc: 'The application environment.',
9    format: ['production', 'development', 'test'],
10    default: 'development',
11    env: 'NODE_ENV'
12  },
13  ip: {
14    doc: 'The IP address to bind.',
15    format: 'ipaddress',
16    default: '127.0.0.1',
17    env: 'IP_ADDRESS',
18  },
19  port: {
20    doc: 'The port to bind.',
21    format: 'port',
22    default: 8080,
23    env: 'PORT',
24    arg: 'port'
25  },
26  db: {
27    host: {
28      doc: 'Database host name/IP',
29      format: '*',
30      default: 'server1.dev.test'
31    },
32    name: {
33      doc: 'Database name',
34      format: String,
35      default: 'users'
36    }
37  },
38  admins: {
39    doc: 'Users with write access, or null to grant full access without login.',
40    format: Array,
41    nullable: true,
42    default: null
43  }
44});
45
46// Load environment dependent configuration
47var env = config.get('env');
48config.loadFile('./config/' + env + '.json');
49
50// Perform validation
51config.validate({allowed: 'strict'});
52
53module.exports = config;

An example server.js file leveraging the config.js file above:

1var http = require('http');
2var config = require('./config.js');
3
4var server = http.createServer(function (req, res) {
5  res.writeHead(200, {'Content-Type': 'text/plain'});
6  res.end('Hello World\n');
7});
8
9// Consume
10server.listen(config.get('port'), config.get('ip'), function(x) {
11  var addy = server.address();
12  console.log('running on http://' + addy.address + ':' + addy.port);
13});

To launch your example server, and set a port:

1node ./server.js --port 8080

Note: Command-line arguments must be supplied with a double-hyphen prefix (e.g. --arg). Single-hypen prefixes (e.g. -a) are not supported at this time.

The Schema

A configuration module, with its deep nested schema, could look like this:

config.js:

1var config = convict({
2  db: {
3    name: {
4      format: String,
5      default: ''
6    },
7    synchro: {
8      active: {
9        format: 'Boolean',
10        default: false
11      },
12      remote_url: {
13        format: 'url',
14        default: 'http://localhost:8080/'
15      }
16    }
17  },
18  secret: {
19    doc: 'Secret used for session cookies and CSRF tokens',
20    format: '*',
21    default: '',
22    sensitive: true
23  }
24});
25
26config.loadFile(['./prod.json', './config.json']);

Each setting in the schema has the following possible properties, each aiding in convict's goal of being more robust and collaborator friendly.

• Type information: the format property specifies either a built-in convict format (ipaddress, port, int, etc.), or it can be a function to check a custom format. During validation, if a format check fails it will be added to the error report.
• Default values: Every setting must have a default value.
• Environmental variables: If the variable specified by env has a value, it will overwrite the setting's default value. An environment variable may not be mapped to more than one setting.
• Command-line arguments: If the command-line argument specified by arg is supplied, it will overwrite the setting's default value or the value derived from env.
• Documentation: The doc property is pretty self-explanatory. The nice part about having it in the schema rather than as a comment is that we can call config.getSchemaString() and have it displayed in the output.
• Sensitive values and secrets: If sensitive is set to true, this value will be masked to "[Sensitive]" when config.toString() is called. This helps avoid disclosing secret keys when printing configuration at application start for debugging purposes.
• Null values: If nullable is set to true, the value counts as valid not only if it matches the specified format, but also when it is null.

Validation

In order to help detect misconfigurations, convict allows you to define a format for each setting. By default, convict checks if the value of the property has the same type (according to Object.prototype.toString.call) as the default value specified in the schema. You can define a custom format checking function in the schema by setting the format property.

convict provides several predefined formats for validation that you can use. Most of them are self-explanatory:

• * - any value is valid
• int
• port
• windows_named_pipe
• port_or_windows_named_pipe
• nat - positive integer (natural number)

You can find other format here.

If format is set to one of the built-in JavaScript constructors, Object, Array, String, Number, RegExp, or Boolean, validation will use Object.prototype.toString.call to check that the setting is the proper type.

If nullable is set to true, null will be a valid value as well.

Custom format checking

You can specify a custom format checking method on a property basis.

For example:

1var config = convict({
2  key: {
3    doc: 'API key',
4    format: function check (val) {
5      if (!/^[a-fA-F0-9]{64}$/.test(val)) {
6        throw new Error('must be a 64 character hex key')
7      }
8    },
9    default: '3cec609c9bc601c047af917a544645c50caf8cd606806b4e0a23312441014deb'
10  },
11  name: {
12    doc: 'user name',
13    format: function check (val) {
14      if (typeof val.first_name !== 'string') {
15        throw new TypeError(`first name '${val.first_name}' is not a string`);
16      }
17      if (typeof val.last_name !== 'string') {
18        throw new TypeError(`last name '${val.last_name}' is not a string`);
19      }
20    },
21    default: {
22      first_name: 'John',
23      last_name: 'Doe'
24    }
25  }
26});

Or, you can use convict.addFormat() to register a custom format checking method that can be reused for many different properties:

1convict.addFormat({
2  name: 'float-percent',
3  validate: function(val) {
4    if (val !== 0 && (!val || val > 1 || val < 0)) {
5      throw new Error('must be a float between 0 and 1, inclusive');
6    }
7  },
8  coerce: function(val) {
9    return parseFloat(val, 10);
10  }
11});
12
13var config = convict({
14  space_used: {
15    format: 'float-percent',
16    default: 0.5
17  },
18  success_rate: {
19    format: 'float-percent',
20    default: 60.0
21  }
22});

The coerce function is optional.

Custom format for array items

You can specify a custom format checking for array items:

1convict.addFormat({
2  name: 'source-array',
3  validate: function(sources, schema) {
4    if (!Array.isArray(sources)) {
5      throw new Error('must be of type Array');
6    }
7
8    for (source of sources) {
9      convict(schema.children).load(source).validate();
10    }
11  }
12});
13
14convict.addFormat(require('convict-format-with-validator').url);
15
16const schema = {
17  sources: {
18    doc: 'A collection of data sources.',
19    format: 'source-array',
20    default: [],
21
22    children: {
23      type: {
24        doc: 'The source type',
25        format: ['git', 'hg', 'svn'],
26        default: null
27      },
28      url: {
29        doc: 'The source URL',
30        format: 'url',
31        default: null
32      }
33    }
34  }
35};
36
37convict(schema).load({
38  'sources': [
39    {
40      'type': 'git',
41      'url': 'https://github.com/mozilla/node-convict.git'
42    },
43    {
44      'type': 'git',
45      'url': 'https://github.com/github/hub.git'
46    }
47  ]
48}).validate();

Coercion

Convict will automatically coerce environmental variables from strings to their proper types when importing them. For instance, values with the format int, nat, port, or Number will become numbers after a straight forward parseInt or parseFloat. duration and timestamp are also parse and converted into numbers, though they utilize moment.js for date parsing.

Precedence order

When merging configuration values from different sources, Convict follows precedence rules. The order, from lowest to highest, for config.loadFile(file) and config.load(json) is:

1. Default value
2. File or json set in function argument
3. Environment variables (only used when env property is set in schema)
4. Command line arguments (only used when arg property is set in schema)

This order means that if schema defines parameter to be taken from an environment variable and environment variable is set then you cannot override it with config.loadFile(file) or config.load(json).

1process.env.PORT = 8080; // environment variable is set
2const config = convict({
3  port: {
4    default: 3000,
5    env: 'PORT'
6  }
7});
8config.load({ port: 9000 });
9console.log(config.get('port')); // still 8080 from env

Overriding Environment variables and Command line arguments

Convict allows to override Environment variables and Command line arguments. It can be helpful for testing purposes.

When creating a config object pass an object with two optional properties as the 2nd parameter:

• env: Object - this object will be used instead of process.env
• args: Array<string> - this array will be used instead of process.argv

1var config = convict({
2  // configuration schema
3}, {
4  env: {
5    // Environment variables
6  },
7  args: [
8    // Command line arguments
9  ]
10});

Configuration file additional types support

Convict is able to parse files with custom file types during loadFile. For this specify the corresponding parsers with the associated file extensions.

1convict.addParser({ extension: 'toml', parse: toml.parse });
2convict.addParser({ extension: ['yml', 'yaml'], parse: yaml.load });
3convict.addParser([
4  { extension: 'json', parse: JSON.parse },
5  { extension: 'json5', parse: json5.parse },
6  { extension: ['yml', 'yaml'], parse: yaml.load },
7  { extension: 'toml', parse: toml.parse }
8]);
9
10const config = convict({ ... });
11config.loadFile('config.toml');

If no supported extension is detected, loadFile will fallback to using the default json parser.

Allow comments in JSON files

If you want to allow comments in your JSON file, use JSON5.

1convict.addParser({extension: 'json', parse: require('json5').parse});

API

var config = convict(schema[, opts])

convict() takes a schema object or a path to a schema JSON file and returns a convict configuration object.

opts: Optional object:

• opts.env: Override process.env if specified using an object {'NODE_ENV': 'production'}.
• opts.args: Override process.argv if specified using an array ['--argname', 'value'] or a string --argname value.

The configuration object has an API for getting and setting values, described below.

1var config = convict({
2  env: {
3    doc: 'The application environment.',
4    format: ['production', 'development', 'test'],
5    default: 'development',
6    env: 'NODE_ENV'
7  },
8  log_file_path: {
9    'doc': 'Log file path',
10    'format': String,
11    'default': '/tmp/app.log'
12  }
13});
14
15// or
16config = convict('/some/path/to/a/config-schema.json');

convict.addParser(parser or parserArray)

Adds new parsers for custom file extensions

convict.addFormat(format) or convict.addFormat(name, validate, coerce)

Adds a new custom format, format being an object, see example below.

1convict.addFormat({
2  name: 'float-percent',
3  validate: function(val) {
4    if (val !== 0 && (!val || val > 1 || val < 0)) {
5      throw new Error('must be a float between 0 and 1, inclusive');
6    }
7  },
8  coerce: function(val) {
9    return parseFloat(val, 10);
10  }
11});

convict.addFormats(formats)

Adds new custom formats, formats being an object whose keys are the new custom format names, see example below.

1convict.addFormats({
2  prime: {
3    validate: function(val) {
4      function isPrime(n) {
5        if (n <= 1) return false; // zero and one are not prime
6        for (let i=2; i*i <= n; i++) {
7          if (n % i === 0) return false;
8        }
9        return true;
10      }
11      if (!isPrime(val)) throw new Error('must be a prime number');
12    },
13    coerce: function(val) {
14      return parseInt(val, 10);
15    }
16  },
17  'hex-string': {
18    validate: function(val) {
19      if (/^[0-9a-fA-F]+$/.test(val)) {
20        throw new Error('must be a hexadecimal string');
21      }
22    }
23  }
24});

config.get(name)

Returns the current value of the name property. name can use dot notation to reference nested values. E.g.:

1config.get('db.host');
2
3// or
4config.get('db').host;

config.default(name)

Returns the default value of the name property. name can use dot notation to reference nested values. E.g.:

1config.default('server.port');

config.reset(name)

Resets a property to its default value as defined in the schema. E.g.:

1config.reset('server.port');

config.has(name)

Returns true if the property name is defined, or false otherwise. E.g.:

1if (config.has('some.property')) {
2  // Do something
3}

config.set(name, value)

Sets the value of name to value. name can use dot notation to reference nested values, e.g. "db.port". If objects in the chain don't yet exist, they will be initialized to empty objects. E.g.:

1config.set('property.that.may.not.exist.yet', 'some value');
2config.get('property.that.may.not.exist.yet');
3// Returns "some value"

If you call config.load or config.loadFile after config.set then value provided by config.set will be overridden in case of conflict.

config.load(object)

Loads and merges a JavaScript object into config. E.g.:

1config.load({
2  'env': 'test',
3  'ip': '127.0.0.1',
4  'port': 80
5});

config.loadFile(file or fileArray)

Loads and merges one or multiple JSON configuration files into config. E.g.:

1config.loadFile('./config/' + conf.get('env') + '.json');

Or, loading multiple files at once:

1// CONFIG_FILES=/path/to/production.json,/path/to/secrets.json,/path/to/sitespecific.json
2config.loadFile(process.env.CONFIG_FILES.split(','));

config.validate([options])

Validates config against the schema used to initialize it. All errors are collected and thrown or displayed at once.

allowed option

1. warn: If set to warn (that is {allowed: 'warn'} is passed), any properties specified in config files that are not declared in the schema will print a warning. This is the default behavior.

2. strict: If set to strict (that is {allowed: 'strict'} is passed), any properties specified in config files that are not declared in the schema will throw errors. This is to ensure that the schema and the config files are in sync.

3. output : You can replace the default output console.log by your own output function. You can use debug module like this:

   1  output: require('debug')('convict:validate:error')

config.getProperties()

Exports all the properties (that is the keys and their current values) as JSON.

config.toString()

Exports all the properties (that is the keys and their current values) as a JSON string, with sensitive values masked. Sensitive values are masked even if they aren't set, to avoid revealing any information.

config.getSchema()

Exports the schema as JSON.

config.getSchemaString()

Exports the schema as a JSON string.

config.getArgs()

The array of process arguments (not including the launcher and application file arguments). Defaults to process.argv unless an override is specified using the args key of the second (options) argument of the convict function.

config.getEnv()

The map of environment variables. Defaults to process.env unless an override is specified using the env key of the second argument (options) argument of the convict function.

FAQ

How can I define a configuration property as "required" without providing a default value?

The philosophy was to have production values be the default values. Usually you only want to change defaults for deploy or instance (in aws speak) specific tweaks. However, you can set a default value to null and if your format doesn't accept null it will throw an error.

How can I use convict in a (browserify-based) browser context?

Thanks to browserify, convict can be used for web applications too. To do so,

• Use brfs to ensure the fs.loadFileSync schema-loading calls are inlined at build time rather than resolved at runtime (in Gulp, add .transform(brfs) to your browserify pipe).
• To support "loading configuration from a http://foo.bar/some.json URL", build a thin wrapper around convict using your favorite http package (e.g. superagent). Typically, in the success callback, call convict's load() on the body of the response.

Migrating

• Migrating from Convict 5 to 6