Configuration Methods
There are three ways to configure doc-kit, listed in order of precedence (highest to lowest):- Configuration file - Pass a custom config file using
--config-file - CLI options - Override specific settings via command-line arguments
- Default values - Built-in defaults used when no configuration is provided
Configuration File Support
Configuration files must be loadable via animport() call. Supported formats include:
- JavaScript/ESM (
.mjs,.jswith"type": "module") - JSON (
.json)
- JavaScript
- JSON
Using a Configuration File
Pass your configuration file to doc-kit using the--config-file option:
Configuration Structure
A doc-kit configuration object consists of:global- Settings that apply to all generators unless overriddenthreads- Number of worker threads to use for parallel processingchunkSize- Number of items to process per worker threadtarget- Array of generator names to run- Generator-specific overrides - Per-generator configuration that inherits from
global
Configuration Merging
When multiple configuration sources are provided, doc-kit merges them using a deep merge strategy:- Start with built-in defaults
- Apply configuration file settings
- Apply CLI option overrides
Next Steps
File Format
Learn about the configuration file structure and all available properties
CLI Options
See how CLI options map to configuration properties