mfer 1.0.2 → 1.0.3

package/README.md

@@ -10,15 +10,6 @@ A powerful CLI tool designed to simplify the management and execution of multipl
 - [📦 Installation](#-installation)
 - [🛠️ Quick Start](#️-quick-start)
 - [📋 Commands](#-commands)
-  - [mfer init](#mfer-init)
-  - [mfer run](#mfer-run)
-  - [mfer pull](#mfer-pull)
-  - [mfer install](#mfer-install)
-  - [mfer clone](#mfer-clone)
-  - [mfer config](#mfer-config)
-    - [mfer config list](#mfer-config-list)
-    - [mfer config edit](#mfer-config-edit)
-  - [mfer help](#mfer-help)
 - [⚙️ Configuration](#️-configuration)
 - [🎯 Use Cases](#-use-cases)
 - [🔧 Advanced Usage](#-advanced-usage)
@@ -93,6 +84,15 @@ mfer pull frontend
 
 ## 📋 Commands
 
+### Quick Reference
+- [`mfer init`](#mfer-init) - Interactive setup wizard
+- [`mfer run`](#mfer-run-group_name) - Run micro frontend applications
+- [`mfer pull`](#mfer-pull-group_name) - Pull latest changes from git repositories
+- [`mfer install`](#mfer-install-group_name) - Install dependencies for micro frontends
+- [`mfer clone`](#mfer-clone-group_name) - Clone repositories that don't exist locally
+- [`mfer config`](#mfer-config) - Manage configuration settings
+- [`mfer help`](#mfer-help) - Display help information
+
 ### `mfer init`
 Interactive setup wizard to create your configuration file.
 
@@ -265,7 +265,11 @@ groups:
 ## 🔧 Advanced Usage
 
 ### Custom Start Commands
-By default, mfer runs `npm start` in each project directory. You can customize this by modifying the run command in the source code.
+By default, mfer runs `npm start` in each project directory. 
+You can currently only customize this by modifying the run command in the source code.
+
+Adding configurable custom start commands is something I plan on adding in the near future. 
+I also welcome anyone to open a PR for that!
 
 ### Environment Variables
 mfer respects your existing environment setup and will use the same Node.js and npm versions you have configured.

package/dist/commands/run.js

@@ -3,6 +3,7 @@ import { configExists, currentConfig, warnOfMissingConfig, } from "../utils/conf
 import concurrently from "concurrently";
 import chalk from "chalk";
 import path from "path";
+const RUN_COMMAND = "npm start";
 const runCommand = new Command("run")
     .description("run micro-frontend applications")
     .argument("[group_name]", "name of the group as specified in the configuration", "all")
@@ -25,7 +26,7 @@ const runCommand = new Command("run")
     }
     const mfeDir = currentConfig.mfe_directory;
     const commands = group.map((mfe) => ({
-        command: "npm start",
+        command: RUN_COMMAND,
         name: mfe,
         cwd: path.join(mfeDir, mfe),
         prefixColor: "blue"

package/dist/index.js

@@ -10,7 +10,7 @@ import { loadConfig } from "./utils/config-utils.js";
 program
     .name("mfer")
     .description("Micro Frontend Runner (mfer) - A CLI for running your project's micro frontends.")
-    .version("1.0.2", "-v, --version", "mfer CLI version")
+    .version("1.0.3", "-v, --version", "mfer CLI version")
     .hook("preAction", (thisCommand, actionCommand) => {
     console.log();
 })

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mfer",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "CLI tool designed to sensibly run micro-frontends from the terminal.",
   "bin": {
     "mfer": "dist/index.js"