A lightweight and flexible configuration management library for Node.js applications. Multiconf simplifies working with JSON and JSONC configuration files, supporting both user-defined and default configurations with environment variable overrides.
- 📁 Simple JSON/JSONC configuration management
- 🔄 Automatic fallback to default configurations
- 💬 JSONC support (JSON with comments)
- 🌍 Environment variable overrides
- 🚀 Lightweight and zero-dependencies
npm install multiconf
const Multiconf = require('multiconf');
// Initialize with default config directory (./conf)
const conf = Multiconf.get();
// Or specify a custom config directory
const conf = Multiconf.get('./config');
Multiconf supports two types of configuration files:
-
User Configurations (
*.json
or*.jsonc
) -
Default Configurations (
*.json.default
or*.jsonc.default
)
The library will first look for user configurations, falling back to default configurations if not found.
./conf/server.json.default
:
{
"hostname": "localhost",
"port": 3141,
"token": "<default-token>"
}
./conf/server.json
:
{
"hostname": "localhost",
"port": 3141,
"token": "QWERTY-123456"
}
// Access configuration values
console.log(`${conf.server.hostname}:${conf.server.port}`); // "localhost:3141"
console.log(`Token is ${conf.server.token}`); // "Token is QWERTY-123456"
Multiconf supports JSONC (JSON with comments) format:
Note: JSONC files have higher priority than JSON files. If both
server.jsonc
andserver.json
exist,server.jsonc
will be used.
Override configuration values using environment variables:
// Initialize with environment variable prefix
const conf = Multiconf.get('./conf', 'APP_CONF_');
Set environment variables to override configurations:
# Override server configuration
APP_CONF_server='{"token":"env-token-12345"}'
Environment variables must contain valid JSON strings that will be parsed and merged into your configuration.
MIT © 2017-2025 Volodymyr Sichka