A config parser you can use in your apps. It supports hot-reloading, yaml, ini, json and jsonc.
MIT License
Join my discord server or visit my website.
It's a package that parses config files from different languages. It can reload them once they change and features a custom parser and validator. It supports as of now:
The parser will ignore any binary files.
JS
const ConfigParser = require("@backs/config-parser")
const { mySchema } = require("./schemas")
const { myValidator } = require("./validators")
const parser = new ConfigParser({
files: {
bot: {
path: "./configs/bot.json",
validator: mySchema
},
server: {
path: "./configs/server.yaml",
hotReload: false,
validator: myValidator
}
},
folders: [{
path: "./other/configs/*"
}],
start: false
})
// Types will be any so no intellisense
parser.start.then(() => console.log(
parser.configs.bot,
parser.configs.server,
// If other/configs has a file named test, view options for more customization of the name
parser.configs.test
))
TS
import ConfigParser from "@backs/config-parser"
import { mySchema } from "./schemas"
import { myValidator } from "./validators"
const parser = new ConfigParser<MyConfigType>({
files: {
bot: {
path: "./configs/bot.json",
validator: mySchema
},
server: {
path: "./configs/server.yaml",
hotReload: false,
validator: myValidator
}
},
folders: [{
path: "./other/configs/*"
}],
start: false
})
// Types will be the types of MyConfigType
parser.start.then(() => console.log(
parser.configs.bot,
parser.configs.server,
// If other/configs has a file named test, view options for more customization of the name
parser.configs.test
))
If you set
start
to false, you will need to manually start the parser
parser.start()
You can also stop the parser. Useful when watching for changes.
parser.stop()
Let's say you're using a not-so-common file type. Well you're not out of luck, you can just pass a custom function parser to parse it. Your function should take a string and return any type value. Your function can be both synchronous or asynchronous. Example:
import ConfigParser from "@backs/config-parser"
const parser = new ConfigParser({
files: {
myWeirdFile: {
path: "./path/to/my/config.weirdextension",
parser: async (config) => {
return await myWeirdParser.parse(config)
}
}
},
folders: {}
})
console.log(parser.configs.myWeirdFile)
If you're using the
folders
option to load your files and need a custom parser, you must add each file manually to thefiles
option instead.
You can listen to chokidar events by passing the events to the events property, more info in the events
option below.
hotReload
?: boolean
- Whether or not to watch the files for changes using chokidar and reload them once they change. Defaults to true
.allowBinary
?: boolean
- Whether or not to allow binary files. Defaults to false
.watchOptions
?: ChokidarWatchOptions
- Just the watch options from chokidar.globOptions
?: GlobOptionsWithFileTypesUnset | GlobOptionsWithFileTypesFalse
- Just the globOptions from glob. The option withFileTypes
must be undefined
or false
.
conserveExtensions
?: boolean
- Whether or not to conserve extensions of files when using the folders
option to load files. Defaults to false
.conservePaths
?: boolean
- Whether or not to conserve the full file path of files when using the folders
option to load files. Useful to avoid conflicts between files named similarly. Setting this option to true will always show the file extension aswell. Defaults to false
.encoding
?: BufferEncoding
- Which encoding to use for all files. Example: utf-16
, base64
... Defaults to utf-8
.start
?: boolean
- Whether to start parsing files as soon as the parser is created or until the start()
function is called. Defaults to true
.files
: Record<string, ConfigFileOptions>
- An object of config names to load and their options.folders
: Record<string, ConfigFolderOptions>
- An object of config folder names to load and their options.parsers
?: Record<string, (config: string) => any | Promise<any>>
- An object containing extensions as keys and custom parser functions as values. The parser will parse any file that has that extension using that function. This overrides the default parsers. Extensions must be preceeded by a dot, example: .myweirdextension
.
logging
?:
error
?: boolean
- Whether or not to log any errors that happen while parsing or loading the files to the console. Defaults to true
.debug
?: boolean
- Whether or not to log additional info about the parser to the console. Defaults to false
.events
?: FSWatcherEvents
- An object containing name of the chokidar event with a function to handle it.path
: string
- The path to file.hotReload
?: boolean
- Whether or not to watch this file for changes. Overrides the global hotReload
.allowBinary
?: boolean
- Whether or not to allow the file even if it is a binary file. Defaults to false
.parser
?: (config: string) => any | Promise<any>
- The custom parser for your file. This is entirely optional. The parser will parse any file that is supported and will leave the rest as a string
.validator
?: Joi.Schema | Zod.Schema | ((config: any) => boolean)
- Can be either a Joi Schema or a function that takes the parsed file and returns a boolean.path
: string
- The glob pattern to the files in a specific folder.hotReload
?: boolean
- Whether or not to watch this files in this folder for changes. Overrides the global hotReload
.allowBinary
?: boolean
- Whether or not to allow binary files. Defaults to false
.parsers
?: Record<string, (config: string) => any | Promise<any>>
- An object containing exact file names (includes extension without the path) as keys and custom parser functions as values. The parser will use this function to parse that specific file.validators
?: Record<string, Joi.Schema | Zod.Schema | ((config: any) => boolean)>
- An object containing exact file names (includes extension without the path) as keys and validators as values.If you encounter any issues or have any suggestions, please make a github issue/comment/pr.