@maka/maka-cli 5.2.11 → 5.3.0

package/.github/workflows/npm-publish.yml

@@ -1,11 +1,16 @@
-# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
+# This workflow runs tests on every push to master, when a GitHub Release is
+# created, or manually via workflow_dispatch, and publishes to npm only when
+# package.json's version differs from what's currently live on the registry.
 # For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages
 
 name: Node.js Package
 
 on:
+  push:
+    branches: [master]
   release:
     types: [created]
+  workflow_dispatch:
 
 jobs:
   build:
@@ -32,4 +37,18 @@ jobs:
           registry-url: https://registry.npmjs.org/
       - run: npm ci
       - run: npm install -g npm@latest # trusted publishing needs npm >=11.5.1
-      - run: npm publish --access public
+      - name: Check if version changed
+        id: version-check
+        run: |
+          LOCAL_VERSION=$(node -p "require('./package.json').version")
+          PUBLISHED_VERSION=$(npm view "$(node -p "require('./package.json').name")" version 2>/dev/null || echo "none")
+          echo "Local version: $LOCAL_VERSION"
+          echo "Published version: $PUBLISHED_VERSION"
+          if [ "$LOCAL_VERSION" != "$PUBLISHED_VERSION" ]; then
+            echo "should_publish=true" >> "$GITHUB_OUTPUT"
+          else
+            echo "should_publish=false" >> "$GITHUB_OUTPUT"
+          fi
+      - name: Publish to npm
+        if: steps.version-check.outputs.should_publish == 'true'
+        run: npm publish --access public

package/eslint.config.js

@@ -5,12 +5,21 @@ import tseslint from "typescript-eslint";
 
 export default [
   {files: ["**/*.{js,mjs,cjs,ts}"]},
-  {languageOptions: { globals: globals.browser }},
+  {languageOptions: { globals: globals.browser, parserOptions: { project: "./tsconfig.json" } }},
   pluginJs.configs.recommended,
   ...tseslint.configs.recommended,
   {
     rules: {
       "@typescript-eslint/no-explicit-any": "off",
+      "@typescript-eslint/no-floating-promises": "error",
+      "@typescript-eslint/no-misused-promises": "error",
+      "@typescript-eslint/prefer-promise-reject-errors": "error",
+      "@typescript-eslint/only-throw-error": "error",
+      "@typescript-eslint/no-unused-vars": ["error", {
+        argsIgnorePattern: "^_",
+        varsIgnorePattern: "^_",
+        destructuredArrayIgnorePattern: "^_",
+      }],
     },
   },
   {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maka/maka-cli",
-  "version": "5.2.11",
+  "version": "5.3.0",
   "type": "module",
   "summary": "A command line tool for scaffolding Meteor 2.x applications using either React.",
   "description": "A command line tool for scaffolding Meteor 2.x applications using React.",
@@ -33,80 +33,67 @@
   "author": "Maka <maka@maka-cli.com>",
   "license": "MIT",
   "dependencies": {
-    "@aws-sdk/client-ec2": "^3.683.0",
-    "@aws-sdk/client-ecr": "^3.682.0",
-    "@aws-sdk/client-route-53": "^3.683.0",
-    "@aws-sdk/client-route-53-domains": "^3.682.0",
+    "@aws-sdk/client-ec2": "^3.1111.0",
+    "@aws-sdk/client-ecr": "^3.1111.0",
+    "@aws-sdk/client-route-53": "^3.1111.0",
+    "@aws-sdk/client-route-53-domains": "^3.1111.0",
     "@babel/eslint-parser": "^7.25.9",
-    "@inquirer/prompts": "^7.0.1",
+    "@inquirer/prompts": "^8.5.2",
     "@maka/tar": "^6.2.2",
-    "@modelcontextprotocol/sdk": "^1.20.0",
     "blessed": "^0.1.81",
     "change-case": "^5.4.4",
     "cli-color": "^2.0.4",
     "cli-cursor": "^5.0.0",
     "cli-table": "^0.3.11",
-    "cors": "^2.8.5",
     "date-fns": "^4.1.0",
     "delete": "github:maka-io/delete",
-    "dotenv": "^16.4.5",
-    "ejs": "^3.1.10",
+    "dotenv": "^17.4.2",
+    "ejs": "^6.0.1",
     "elegant-spinner": "^3.0.0",
     "eslint": "^9.13.0",
-    "express": "^5.1.0",
     "http-proxy": "^1.18.1",
     "humps": "^2.0.1",
     "husky": "^9.1.6",
-    "jest": "^29.7.0",
+    "jest": "^30.4.2",
     "latest-version": "^9.0.0",
     "minimist": "^1.2.8",
     "node-forge": "^1.3.1",
-    "open": "^10.1.0",
     "rimraf": "^6.0.1",
     "semver": "^7.6.3",
     "single-line-log2": "^1.1.3",
     "slash": "^5.1.0",
     "spawn-args": "0.2.0",
     "tar": "^7.4.3",
-    "type-fest": "^4.26.1",
-    "uuid": "^11.0.2",
-    "xtend": "^4.0.2",
-    "zod": "^3.24.1"
+    "uuid": "^14.0.1",
+    "xtend": "^4.0.2"
   },
   "devDependencies": {
-    "@aws-sdk/types": "^3.679.0",
+    "@aws-sdk/types": "^3.974.4",
     "@eslint/js": "^9.13.0",
     "@types/blessed": "^0.1.25",
-    "@types/chai": "^5.0.1",
     "@types/cli-color": "^2.0.6",
     "@types/cli-table": "^0.3.4",
-    "@types/cors": "^2.8.17",
     "@types/ejs": "^3.1.5",
-    "@types/express": "^5.0.0",
     "@types/fibers": "^3.1.4",
     "@types/http-proxy": "^1.17.15",
     "@types/humps": "^2.0.6",
     "@types/inquirer": "^9.0.7",
-    "@types/jest": "^29.5.14",
+    "@types/jest": "^30.0.0",
     "@types/jsonwebtoken": "^9.0.7",
     "@types/meteor": "^2.9.8",
     "@types/minimist": "^1.2.5",
     "@types/node": "^22.8.5",
-    "@types/react": "^18.3.12",
-    "@types/react-dom": "^18.3.1",
     "@types/uuid": "^10.0.0",
-    "aws-sdk": "^2.1691.0",
-    "chai": "^5.1.2",
     "chdir": "^0.0.0",
     "concat-stream": "^2.0.0",
-    "concurrently": "^9.0.1",
-    "esbuild": "^0.25.11",
-    "globals": "^15.11.0",
+    "concurrently": "^10.0.5",
+    "esbuild": "^0.28.2",
+    "globals": "^17.11.0",
     "mkdirp": "^3.0.1",
     "ts-jest": "^29.2.5",
-    "typescript": "^5.6.3",
-    "typescript-eslint": "^8.12.2",
-    "wait-on": "^8.0.1"
+    "typescript": "^6.0.3",
+    "typescript-eslint": "^8.67.0",
+    "wait-on": "^9.1.0"
   },
   "engines": {
     "node": ">=22.17.0",

package/tsconfig.json

@@ -1,5 +1,6 @@
 {
   "compilerOptions": {
+    "ignoreDeprecations": "6.0",
     "esModuleInterop": true,
     "target": "esnext",
     "module": "esnext",
@@ -11,6 +12,7 @@
     "forceConsistentCasingInFileNames": true,
     "declaration": true,
     "strictNullChecks": true,
+    "strictPropertyInitialization": true,
     "resolveJsonModule": true,
     "moduleResolution": "node",
     "sourceMap": true,

package/docs/MCP_SERVER.md

@@ -1,396 +0,0 @@
-# Maka CLI MCP Server
-
-The Maka CLI includes an enhanced Model Context Protocol (MCP) server that exposes **all maka-cli capabilities** to AI agents like Claude. This allows AI assistants to discover, understand, and help you use any maka-cli command.
-
-## Quick Start
-
-Start the MCP server:
-
-```bash
-maka ai:mcp
-```
-
-The server starts on `http://localhost:3000` by default and automatically discovers all available maka-cli commands.
-
-## Options
-
-- `--port` - Port to listen on (default: 3000)
-- `--host` - Host to bind to (default: localhost)
-
-### Examples
-
-```bash
-# Start on default port
-maka ai:mcp
-
-# Custom port
-maka ai:mcp --port=8080
-
-# Bind to all network interfaces
-maka ai:mcp --host=0.0.0.0 --port=3001
-```
-
-## Server Features
-
-### Tools
-
-The MCP server provides these tools for AI agents:
-
-#### 1. `list-maka-commands`
-List all available Maka CLI commands with descriptions and usage.
-
-**Parameters:**
-- `filter` (optional): Filter commands by name or category (e.g., "aws", "generate", "deploy")
-
-**Example Usage:**
-```json
-{
-  "name": "list-maka-commands",
-  "arguments": {
-    "filter": "generate"
-  }
-}
-```
-
-#### 2. `get-command-info`
-Get detailed information about a specific command including usage, options, examples, and description.
-
-**Parameters:**
-- `command` (required): Command name (e.g., "create", "generate:component", "aws:create-instance")
-
-**Example Usage:**
-```json
-{
-  "name": "get-command-info",
-  "arguments": {
-    "command": "generate:component"
-  }
-}
-```
-
-#### 3. `execute-maka-command`
-Execute Maka CLI commands with safety restrictions to prevent destructive operations.
-
-**Parameters:**
-- `command` (required): Full command to execute (e.g., "maka --help")
-- `workingDirectory` (optional): Working directory for the command
-
-**Safety Features:**
-- Blocks destructive commands (murder, uninstall, rm, delete)
-- 30-second timeout
-- 10MB output buffer limit
-
-**Example Usage:**
-```json
-{
-  "name": "execute-maka-command",
-  "arguments": {
-    "command": "maka --help"
-  }
-}
-```
-
-#### 4. `get-project-info`
-Get information about the current Maka project including configuration.
-
-**Example Usage:**
-```json
-{
-  "name": "get-project-info",
-  "arguments": {}
-}
-```
-
-### Resources
-
-#### 1. `maka://commands/all`
-Complete reference of all Maka CLI commands in JSON format.
-
-**Format:**
-```json
-[
-  {
-    "name": "create",
-    "aliases": "None",
-    "shortDesc": "Create a new Meteor application",
-    "description": "...",
-    "usage": "maka create <app-name>",
-    "examples": ["maka create MyApp"],
-    "validOpts": ["..."],
-    "requiredOpts": [],
-    "experimental": false
-  }
-]
-```
-
-#### 2. `maka://project/config`
-Current project configuration and metadata.
-
-#### 3. `maka://info`
-Maka CLI version, platform, and system information.
-
-### Prompts
-
-Interactive conversation starters for common workflows:
-
-#### 1. `create-component`
-Component creation wizard with examples and best practices.
-
-**Parameters:**
-- `componentName` (required): Name of the component
-- `componentType` (optional): Type (component, page, layout, template)
-
-#### 2. `deploy-help`
-Deployment guide for different platforms and environments.
-
-**Parameters:**
-- `environment` (optional): Target environment (dev, staging, production)
-- `platform` (optional): Deployment platform (aws, docker, custom)
-
-#### 3. `project-setup`
-Interactive guide for setting up a new Maka project.
-
-**Parameters:**
-- `projectType` (optional): Project type (basic, full-stack, api)
-
-## Protocol
-
-The server implements the [Model Context Protocol](https://modelcontextprotocol.io) specification:
-
-- **Transport**: Streamable HTTP (stateless mode)
-- **Format**: Server-Sent Events (SSE)
-- **Message Protocol**: JSON-RPC 2.0
-- **Protocol Version**: 2024-11-05
-
-## Endpoints
-
-- `POST /mcp` - MCP protocol endpoint (Server-Sent Events)
-- `GET /health` - Health check endpoint
-
-## Testing
-
-### Health Check
-```bash
-curl http://localhost:3000/health
-```
-
-### List Available Tools
-```bash
-curl -X POST http://localhost:3000/mcp \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{
-    "jsonrpc": "2.0",
-    "id": 1,
-    "method": "tools/list",
-    "params": {}
-  }'
-```
-
-### Call a Tool
-```bash
-curl -X POST http://localhost:3000/mcp \
-  -H "Content-Type: application/json" \
-  -H "Accept: application/json, text/event-stream" \
-  -d '{
-    "jsonrpc": "2.0",
-    "id": 2,
-    "method": "tools/call",
-    "params": {
-      "name": "list-maka-commands",
-      "arguments": {
-        "filter": "aws"
-      }
-    }
-  }'
-```
-
-## Integrating with Claude Desktop
-
-Add this configuration to your Claude Desktop MCP settings:
-
-```json
-{
-  "mcpServers": {
-    "maka-cli": {
-      "command": "maka",
-      "args": ["ai:mcp", "--port=3000"],
-      "transport": "http",
-      "url": "http://localhost:3000/mcp"
-    }
-  }
-}
-```
-
-Alternatively, run the server manually and configure Claude Desktop to connect to the HTTP endpoint:
-
-```json
-{
-  "mcpServers": {
-    "maka-cli": {
-      "transport": "http",
-      "url": "http://localhost:3000/mcp"
-    }
-  }
-}
-```
-
-## How It Works
-
-### Command Discovery
-
-The MCP server automatically discovers all commands by traversing the Maka CLI command tree:
-
-1. Starts at the root `Maka` command
-2. Recursively explores all subcommands
-3. Extracts metadata (name, description, usage, options, examples)
-4. Filters out internal/hidden commands
-5. Builds a complete command registry
-
-This means **any new command added to maka-cli is automatically exposed** through the MCP server.
-
-### Project Detection
-
-The server detects if you're in a Maka project by looking for `.maka/config.json`. Project-specific information is exposed through the `get-project-info` tool and `maka://project/config` resource.
-
-## Use Cases for AI Agents
-
-With this MCP server, AI agents like Claude can:
-
-1. **Discover Commands**: "What commands are available in maka-cli?"
-2. **Get Help**: "How do I create a new component?"
-3. **Learn Usage**: "Show me examples of the deploy command"
-4. **Execute Commands**: "Run maka --version for me"
-5. **Guide Workflows**: "Walk me through deploying to AWS"
-6. **Project Context**: "What's configured in my current project?"
-
-## Customization
-
-### Adding Custom Tools
-
-Edit `src/commands/ai/mcp.sub.cmd.ts` and add new tools:
-
-```typescript
-server.tool(
-  'my-custom-tool',
-  'Description of what my tool does',
-  {
-    param1: z.string().describe('Description of parameter')
-  },
-  async ({ param1 }) => {
-    // Your tool logic here
-    return {
-      content: [
-        {
-          type: 'text',
-          text: `Result: ${param1}`
-        }
-      ]
-    };
-  }
-);
-```
-
-### Adding Custom Resources
-
-```typescript
-server.resource(
-  'my-resource',
-  'maka://custom/resource',
-  {
-    mimeType: 'application/json',
-    description: 'My custom resource'
-  },
-  async () => {
-    return {
-      contents: [
-        {
-          uri: 'maka://custom/resource',
-          mimeType: 'application/json',
-          text: JSON.stringify({ data: 'value' }, null, 2)
-        }
-      ]
-    };
-  }
-);
-```
-
-### Adding Custom Prompts
-
-```typescript
-server.prompt(
-  'my-workflow',
-  'Guided workflow for a specific task',
-  {
-    taskType: z.enum(['option1', 'option2']).describe('Type of task')
-  },
-  async ({ taskType }) => {
-    return {
-      messages: [
-        {
-          role: 'user',
-          content: {
-            type: 'text',
-            text: `Help me with ${taskType}`
-          }
-        },
-        {
-          role: 'assistant',
-          content: {
-            type: 'text',
-            text: `Here's how to handle ${taskType}...`
-          }
-        }
-      ]
-    };
-  }
-);
-```
-
-## CORS Configuration
-
-The server is configured with CORS enabled for all origins by default. For production:
-
-```typescript
-app.use(cors({
-  origin: 'https://yourdomain.com', // Restrict to specific origin
-  exposedHeaders: ['Mcp-Session-Id']
-}));
-```
-
-## Dependencies
-
-- `@modelcontextprotocol/sdk` - MCP SDK
-- `express` - HTTP server
-- `cors` - CORS middleware
-- `zod` - Schema validation
-
-## Architecture
-
-```
-┌─────────────────┐
-│   AI Agent      │
-│  (e.g. Claude)  │
-└────────┬────────┘
-         │ MCP over HTTP
-         │
-┌────────▼────────┐
-│   MCP Server    │
-│  (ai:mcp cmd)   │
-├─────────────────┤
-│ • Tools         │
-│ • Resources     │
-│ • Prompts       │
-└────────┬────────┘
-         │
-         ├─► Command Discovery (Maka._commands)
-         ├─► Project Detection (.maka/config.json)
-         └─► Command Execution (execSync with safety)
-```
-
-## Resources
-
-- [Model Context Protocol Documentation](https://modelcontextprotocol.io)
-- [MCP SDK on GitHub](https://github.com/modelcontextprotocol/typescript-sdk)
-- [Claude Desktop MCP Integration](https://docs.anthropic.com/claude/docs/model-context-protocol)
-- [Maka CLI Documentation](https://www.maka-cli.com)