configre 1.1.10 → 1.2.2

package/README.md

@@ -7,7 +7,7 @@ Welcome to Configre, the coolest way to manage your project's configuration with
 - **Environment-Specific Configurations**: Automatically loads configurations based on the hostname or a custom profile forced via `--config=<profile>` CLI argument.
 - **Fallback to Defaults**: Uses a default configuration as a baseline, ensuring your application always has the necessary settings.
 - **Easy Integration**: A simple setup process that integrates effortlessly into any project.
-- **Support for `.cjs` Config Files**: Config files must use the `.cjs` extension. This allows dynamic configuration values and comments, and works the same in both CommonJS and ESM projects.
+- **Support for `.cjs` Config Files Only**: Config files must use the `.cjs` extension. This allows dynamic configuration values and comments, and works the same in both CommonJS and ESM projects.
 
 ## 🌟 Getting Started
 
@@ -34,7 +34,7 @@ To get started with Configre, follow these steps:
    - `[hostname].cjs`: Override configurations for specific hosts.
    - `[hostname].dev.cjs`: Development-specific configurations.
 
-   > **Note:** Config files must always use the `.cjs` extension. That way they work in both CommonJS and ESM projects and you can use `module.exports` in them.
+   > **Note:** Config files must always use the `.cjs` extension; `.js` config files are not accepted. That way they work in both CommonJS and ESM projects and you can use `module.exports` in them.
 
 3. **Use Configre in Your Project**
 
@@ -80,16 +80,17 @@ module.exports = {
 
 Configre merges these configurations based on your environment, making your app adaptable and easier to manage.
 
-## 🎯 Forcing a Profile
+## 🎯 Forcing a hostname / config
 
-You can override the hostname-based profile detection by passing `--config=<profile>` anywhere in the CLI arguments:
+By default Configre uses the machine’s hostname to choose the config file (e.g. `config/<hostname>.cjs`). You can force which hostname or profile to use with the `--config=<hostname>` CLI argument:
 
 ```bash
-node app.js --config=staging
-node app.js --port=3000 --config=production --debug
+node demo.js --config=staging
+node demo.js --config=production
+node demo.js --port=3000 --config=myhost --debug
 ```
 
-This loads `config/staging.cjs` (or `config/staging.dev.cjs`) regardless of the hostname. The `--config=` flag is safe to use alongside any other arguments.
+This loads `config/staging.cjs` (or `config/staging.dev.cjs`) instead of the one for the actual hostname. The `--config=` flag can appear anywhere in the command and works alongside other arguments.
 
 ## 🤔 Why Configre?
 

package/index.js

@@ -1,20 +1,27 @@
 const fs = require("fs");
+const path = require("path");
 const os = require("os");
 const obj = require("lodash/object");
 const log = require("lemonlog")("Configre");
 
 class ConfigreClass {
-    constructor(path = __dirname + "/../../config") {
+    constructor(pathOrDir = __dirname + "/../../config") {
+        const dir = path.join(pathOrDir);
+        const isNested = (ConfigreClass._nesting || 0) > 0;
+        ConfigreClass._nesting = (ConfigreClass._nesting || 0) + 1;
+
         this.defaultSettings = this.tryRequire([
-            path,
-            path + '/index.cjs',
-            path + '.cjs'
+            dir,
+            path.join(dir, "index.cjs"),
+            pathOrDir + ".cjs"
         ]);
-        
-        this.dirname = path;
+
+        this.dirname = dir;
+        this._isNested = isNested;
         const configArg = process.argv.find(arg => arg.startsWith('--config='));
         this.profile = configArg ? configArg.slice('--config='.length) : os.hostname();
         this.profileSettings = this.loadProfileSettings();
+        ConfigreClass._nesting -= 1;
     }
 
     // Helper method to try requiring files with different extensions or paths
@@ -29,33 +36,33 @@ class ConfigreClass {
         throw new Error(`Could not load config from any of: ${paths.join(', ')}`);
     }
 
-    // Helper method to try loading a file with .js or .cjs extension
+    // Helper method to try loading a file with .cjs extension only
     tryRequireWithExtensions(basePath) {
-        const extensions = ['.js', '.cjs'];
-        for (const ext of extensions) {
-            const fullPath = basePath + ext;
-            if (fs.existsSync(fullPath)) {
-                return { path: fullPath, module: require(fullPath) };
-            }
+        const ext = '.cjs';
+        const fullPath = path.join(basePath + ext);
+        if (fs.existsSync(fullPath)) {
+            return { path: fullPath, module: require(fullPath) };
         }
         return null;
     }
 
     loadProfileSettings() {
         const basePaths = [
-            { base: `${this.dirname}/${this.profile}.dev`, type: "DEV CONFIG" },
-            { base: `${this.dirname}/${this.profile}`, type: "PRO CONFIG" }
+            { base: path.join(this.dirname, `${this.profile}.dev`), type: "DEV CONFIG" },
+            { base: path.join(this.dirname, this.profile), type: "PRO CONFIG" }
         ];
 
         for (const { base, type } of basePaths) {
             const result = this.tryRequireWithExtensions(base);
             if (result) {
-                log.warn(result.path, type);
+                if (!this._isNested) log.warn(result.path, type);
                 return result.module;
             }
         }
 
-        log.warn(`${this.dirname}/${this.profile}.js`, "NOT FOUND, USING DEFAULTS");
+        if (!this._isNested) {
+            log.warn(path.join(this.dirname, `${this.profile}.cjs`), "NOT FOUND, USING DEFAULTS");
+        }
         return {};
     }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "configre",
-  "version": "1.1.10",
+  "version": "1.2.2",
   "description": "🔧 Effortlessly Tailor Your Settings",
   "dependencies": {
     "lemonlog": "^1.0.2",

package/skills/configre/SKILL.md

@@ -112,5 +112,5 @@ Result: staging overrides are merged over defaults, without conflicting with oth
 ## Key behaviors
 
 - **Deep merge**: nested objects merge recursively via lodash `_.merge`
-- **Config files must use the `.cjs` extension** (works in both CommonJS and ESM projects)
+- **Config files must use the `.cjs` extension** (`.js` is not accepted; works in both CommonJS and ESM projects)
 - **Function vs constructor**: `Configre(path)` returns the merged config directly; `new Configre(path)` returns the instance (use `.get()` to retrieve config)