🧩 hbh-ccl

A lightweight and flexible custom config loader for Node.js (ESM-only) projects.

hbh-ccl helps you load a configuration file from your project directory — either from the root or ./config/ folder — and gracefully fall back to a default config if none is provided.

✅ Built for modern ESM syntax
⚡ Async and minimal
🧠 Smart fallback + deep merging

---

✨ Features

• ✅ Loads user-defined config from:
  • ./<configName> or
  • ./config/<configName>
• 🔄 Falls back to a default config path (relative or absolute)
• 🧠 Supports both export default and full module exports
• ⚡ Fully async and non-blocking
• 🗂️ ESM-only (no .json, .cjs, or CommonJS)
• 🧪 Clean and testable structure

---

📦 Installation

Install via npm:

          
            1npm install hbh-ccl
          
        

Or using yarn:

          
            1yarn add hbh-ccl
          
        

---

🚀 Usage

1️⃣ Create your config file

Create a config file in your project root or inside config/ folder (optional if you're using fallback only):

          
            1// custom.config.js2export default {3  port: 3000,4  debug: true,5  database: {6    host: 'localhost',7    user: 'root'8  }9};
          
        

2️⃣ Load it in your app

          
            1import { loadConfig } from 'hbh-ccl';3const config = await loadConfig({4  configName: 'custom.config.js',            // optional5  defaultConfigPath: './default.config.js',  // required6  verbose: true                              // optional7});9console.log('Loaded Config:', config);
          
        

🔍 If the config isn’t found in ./ or ./config/, it will load the fallback from defaultConfigPath.

---

📂 Where It Looks for Config

loadConfig() checks for your config in the following order:

1. 📁 ./<configName> (project root)
2. 📁 ./config/<configName> (config subfolder)
3. 🧱 Fallback: defaultConfigPath

This ensures flexibility for both flat and organized project structures.

---

📄 API Reference

loadConfig(options) ⇒ Promise