Simple config handling for your app or module
npm install conf> Simple config handling for your app or module
All you have to care about is what to persist. This module will handle all the dull details like where and how.
It does not support multiple processes writing to the same store.\
I initially made this tool to let command-line tools persist some data.
If you need this for Electron, check out electron-store instead.
``sh`
npm install conf
`js
import Conf from 'conf';
const config = new Conf({projectName: 'foo'});
config.set('unicorn', '🦄');
console.log(config.get('unicorn'));
//=> '🦄'
// Use dot-notation to access nested properties
config.set('foo.bar', true);
console.log(config.get('foo'));
//=> {bar: true}
config.delete('unicorn');
console.log(config.get('unicorn'));
//=> undefined
`
Changes are written to disk atomically, so if the process crashes during a write, it will not corrupt the existing config.
Returns a new instance.
Type: object
#### defaults
Type: object
Default values for the config items.
> [!NOTE]
> The values in defaults will overwrite the default key in the schema option.
#### schema
Type: object
JSON Schema to validate your config data.
This will be the properties object of the JSON schema. That is, define schema as an object where each key is the name of your data's property and each value is a JSON schema used to validate that property.
Example:
`js
import Conf from 'conf';
const schema = {
foo: {
type: 'number',
maximum: 100,
minimum: 1,
default: 50
},
bar: {
type: 'string',
format: 'url'
}
};
const config = new Conf({
projectName: 'foo',
schema
});
console.log(config.get('foo'));
//=> 50
config.set('foo', '1');
// [Error: Config schema violation: foo should be number]`
> [!NOTE]
> The default value will be overwritten by the defaults option if set.
#### rootSchema
Type: object
Top-level properties for the schema, excluding properties field.
Example:
`js
import Conf from 'conf';
const store = new Conf({
projectName: 'foo',
schema: { / … / },
rootSchema: {
additionalProperties: false
}
});
`
#### ajvOptions
Type: object
Under the hood, the JSON Schema validator ajv is used to validate your config. We use JSON Schema draft-2020-12 and support all validation keywords and formats.
> [!NOTE]
> By default, allErrors and useDefaults are both set to true, but can be overridden.
Example:
`js
import Conf from 'conf';
const store = new Conf({
projectName: 'foo',
schema: { / … / },
rootSchema: {
additionalProperties: false
},
ajvOptions: {
removeAdditional: true
}
});
`
#### migrations
Type: object
Important: I cannot provide support for this feature. It has some known bugs. I have no plans to work on it, but pull requests are welcome.
You can use migrations to perform operations to the store whenever a project version is upgraded.
The migrations object should consist of a key-value pair of 'version': handler. The version can also be a semver range.
Example:
`js
import Conf from 'conf';
const store = new Conf({
projectName: 'foo',
projectVersion: …,
migrations: {
'0.0.1': store => {
store.set('debugPhase', true);
},
'1.0.0': store => {
store.delete('debugPhase');
store.set('phase', '1.0.0');
},
'1.0.2': store => {
store.set('phase', '1.0.2');
},
'>=2.0.0': store => {
store.set('phase', '>=2.0.0');
}
}
});
`
> [!NOTE]
> The version the migrations use refers to the project version by default. If you want to change this behavior, specify the projectVersion option.
#### beforeEachMigration
Type: Function\undefined
Default:
The given callback function will be called before each migration step.
The function receives the store as the first argument and a context object as the second argument with the following properties:
- fromVersion - The version the migration step is being migrated from.toVersion
- - The version the migration step is being migrated to.finalVersion
- - The final version after all the migrations are applied.versions
- - All the versions with a migration step.
This can be useful for logging purposes, preparing migration data, etc.
Example:
`js
import Conf from 'conf';
console.log = someLogger.log;
const mainConfig = new Conf({
projectName: 'foo1',
beforeEachMigration: (store, context) => {
console.log([main-config] migrate from ${context.fromVersion} → ${context.toVersion});
},
migrations: {
'0.4.0': store => {
store.set('debugPhase', true);
},
}
});
const secondConfig = new Conf({
projectName: 'foo2',
beforeEachMigration: (store, context) => {
console.log([second-config] migrate from ${context.fromVersion} → ${context.toVersion});`
},
migrations: {
'1.0.1': store => {
store.set('debugPhase', true);
},
}
});
#### configName
Type: string\'config'
Default:
Name of the config file (without extension).
Useful if you need multiple config files for your app or module. For example, different config files between two major versions.
#### projectName
Type: string
Required unless you specify the cwd option.
You can fetch the name field from package.json:
`js
import Conf from 'conf';
import packageJson from './package.json' assert {type: 'json'};
const config = new Conf({projectName: packageJson.name});
`
#### projectVersion
Type: string
Required if you specify the migrations option.
You can fetch the version field from package.json.
#### cwd
Type: string\
Default: System default user config directory
You most likely don't need this. Please don't use it unless you really have to. By default, it will pick the optimal location by adhering to system conventions. You are very likely to get this wrong and annoy users.
Overrides projectName.
By default the config is stored in the system user's config directory; running under another user reads a different store. Set cwd to share across users.
The only use-case I can think of is having the config located in the app directory or on some external storage.
#### encryptionKey
Type: string | Uint8Array | TypedArray | DataView\undefined
Default:
> [!CAUTION]
> This is not intended for security purposes, since the encryption key would be easily found inside a plain-text Node.js app.
Its main use is for obscurity. If a user looks through the config directory and finds the config file, since it's just a JSON file, they may be tempted to modify it. By providing an encryption key, the file will be obfuscated, which should hopefully deter any users from doing so.
When using aes-256-gcm, the config file is authenticated. If the file is changed in any way, the decryption will fail. With aes-256-cbc and aes-256-ctr, tampering can go undetected.
When specified, the store will be encrypted using the encryptionAlgorithm option (defaults to aes-256-cbc).
#### encryptionAlgorithm
Type: 'aes-256-cbc' | 'aes-256-gcm' | 'aes-256-ctr'\'aes-256-cbc'
Default:
Encryption algorithm to use when encryptionKey is set.
Use aes-256-gcm if you want authentication, otherwise use aes-256-cbc or aes-256-ctr.
Changing encryptionAlgorithm will make existing encrypted data unreadable.
When using aes-256-gcm or aes-256-ctr, existing plaintext config files are not supported. Delete the config file or migrate it before enabling encryption. With aes-256-cbc, existing plaintext config files are still readable for backward compatibility.
#### fileExtension
Type: string\'json'
Default:
Extension of the config file.
You would usually not need this, but could be useful if you want to interact with a file with a custom file extension that can be associated with your app. These might be simple save/export/preference files that are intended to be shareable or saved outside of the app.
#### clearInvalidConfig
Type: boolean\false
Default:
The config is cleared if reading the config file causes a SyntaxError (malformed JSON), a schema validation error when using the schema option, or a decryption failure when using encryptionKey. This is a good behavior for unimportant data, as the config file is not intended to be hand-edited, so it usually means the config is corrupt and there's nothing the user can do about it anyway. However, if you let the user edit the config file directly, mistakes might happen and it could be more useful to throw an error when the config is invalid instead of clearing.
#### serialize
Type: Function\value => JSON.stringify(value, null, '\t')
Default:
Function to serialize the config object to a UTF-8 string when writing the config file.
You would usually not need this, but it could be useful if you want to use a format other than JSON.
#### deserialize
Type: Function\JSON.parse
Default:
Function to deserialize the config object from a UTF-8 string when reading the config file.
You would usually not need this, but it could be useful if you want to use a format other than JSON.
#### projectSuffix
Type: string\'nodejs'
Default:
You most likely don't need this. Please don't use it unless you really have to.
Suffix appended to projectName during config file creation to avoid name conflicts with native apps.
You can pass an empty string to remove the suffix.
For example, on macOS, the config file will be stored in the ~/Library/Preferences/foo-nodejs directory, where foo is the projectName.
#### accessPropertiesByDotNotation
Type: boolean\true
Default:
Accessing nested properties by dot notation. For example:
`js
import Conf from 'conf';
const config = new Conf({projectName: 'foo'});
config.set({
foo: {
bar: {
foobar: '🦄'
}
}
});
console.log(config.get('foo.bar.foobar'));
//=> '🦄'
`
Alternatively, you can set this option to false so the whole string would be treated as one key.
`js
import Conf from 'conf';
const config = new Conf({
projectName: 'foo',
accessPropertiesByDotNotation: false
});
config.set({
foo.bar.foobar: '🦄'
});
console.log(config.get('foo.bar.foobar'));
//=> '🦄'
`
#### watch
type: boolean\false
Default:
Watch for any changes in the config file and call the callback for onDidChange or onDidAnyChange if set. This is useful if there are multiple processes changing the same config file.
#### configFileMode
Type: number\0o666
Default:
The mode used when creating the config file.
The mode is modified by the process umask. With the typical umask of 0o022, the default results in 0o644. Config files are also stored in the user's home directory (~/.config/), which is typically protected.
You would usually not need this, but it could be useful if you use a custom cwd. Setting 0o600 would make the file only readable by the owner.
> [!NOTE]
> Setting restrictive permissions can cause problems if different users need to read the file. A common problem is a user running your tool with and without sudo and then not being able to access the config the second time.
You can use dot-notation in a key to access nested properties.
The instance is iterable so you can use it directly in a for…of loop.
#### .set(key, value)
Set an item.
The value must be JSON serializable. Trying to set the type undefined, function, or symbol will result in a TypeError.
#### .set(object)
Set multiple items at once.
#### .get(key, defaultValue?)
Get an item or defaultValue if the item does not exist.
Tip: To get all items, see .store.
#### .reset(...keys)
Reset items to their default values, as defined by the defaults or schema option.
Use .clear() to reset all items.
#### .has(key)
Check if an item exists.
#### .appendToArray(key, value)
Append an item to an array.
If the key doesn't exist, it will be created as an array. If the key exists and is not an array, a TypeError will be thrown.
The value must be JSON serializable. Trying to set the type like undefined, function, or symbol will result in a TypeError.
`js
config.set('items', [{name: 'foo'}]);
config.appendToArray('items', {name: 'bar'});
console.log(config.get('items'));
//=> [{name: 'foo'}, {name: 'bar'}]
// Creates array if key doesn't exist
config.appendToArray('newItems', 'first');
console.log(config.get('newItems'));
//=> ['first']
`
#### .delete(key)
Delete an item.
#### .clear()
Delete all items.
This resets known items to their default values, if defined by the defaults or schema option.
#### .onDidChange(key, callback)
callback: (newValue, oldValue) => {}
Watches the given key, calling callback on any changes.
When a key is first set oldValue will be undefined, and when a key is deleted newValue will be undefined.
Returns a function which you can use to unsubscribe:
`js
const unsubscribe = config.onDidChange(key, callback);
unsubscribe();
`
#### .onDidAnyChange(callback)
callback: (newValue, oldValue) => {}
Watches the whole config object, calling callback on any changes.
oldValue and newValue will be the config object before and after the change, respectively. You must compare oldValue to newValue to find out what changed.
Returns a function which you can use to unsubscribe:
`js
const unsubscribe = config.onDidAnyChange(callback);
unsubscribe();
`
#### .size
Get the item count.
#### .store
Get all the config as an object or replace the current config with an object:
`js`
console.log(config.store);
//=> {name: 'John', age: 30}
`js`
config.store = {
hello: 'world'
};
#### .path
Get the path to the config file.
I'm also the author of configstore. While it's pretty good, I did make some mistakes early on that are hard to change at this point. This module is the result of everything I learned from making configstore. Mainly where the config is stored. In configstore, the config is stored in ~/.config (which is mainly a Linux convention) on all systems, while conf stores config in the system default user config directory. The ~/.config directory, it turns out, often have an incorrect permission on macOS and Windows, which has caused a lot of grief for users.
The serialize and deserialize options can be used to customize the format of the config file, as long as the representation is compatible with utf8 encoding.
Example using YAML:
`js
import Conf from 'conf';
import yaml from 'js-yaml';
const config = new Conf({
projectName: 'foo',
fileExtension: 'yaml',
serialize: yaml.dump,
deserialize: yaml.load
});
`
conf depends on ajv for the schema option, which uses unsafe-eval. Even without using the schema option, ajv is still bundled and may cause CSP errors. As a workaround, you could configure your bundler to replace ajv with a stub:
`js`
// webpack.config.js
module.exports = {
resolve: {
alias: {
'ajv': false,
'ajv-formats': false
}
}
};
Conf is synchronous by design, so this is not possible. As a workaround, you could use make-synchronous to convert asynchrnous functions to synchronous (with caveats):
`js
import Conf from 'conf';
import makeSynchronous from 'make-synchronous';
const config = new Conf({
migrations: {
'0.0.1': store => {
const syncAsyncFunction = makeSynchronous(asyncFunction);
const result = syncAsyncFunction();
store.set('migrated', result);
}
}
});
``
- electron-store - Simple data persistence for your Electron app or module
- cache-conf - Simple cache config handling for your app or module