@maka/maka-cli 5.2.11 → 5.3.1

package/.claude/mcp.json

@@ -1,17 +0,0 @@
-{
-  "mcpServers": {
-    "maka-cli": {
-      "command": "maka",
-      "args": [
-        "ai:mcp",
-        "--port=5050"
-      ],
-      "autoApprove": [
-        "list-maka-commands",
-        "get-command-info",
-        "get-project-info",
-        "get-run-logs"
-      ]
-    }
-  }
-}

package/.eslintrc.json

@@ -1,29 +0,0 @@
-{
-    "env": {
-        "es2021": true,
-        "node": true
-    },
-    "extends": [
-        "eslint:recommended",
-        "plugin:@typescript-eslint/recommended"
-    ],
-    "overrides": [
-    ],
-    "parser": "@typescript-eslint/parser",
-    "parserOptions": {
-        "ecmaVersion": "latest",
-        "sourceType": "module"
-    },
-    "plugins": [
-        "@typescript-eslint"
-    ],
-    "rules": {
-      "@typescript-eslint/ban-types": "off",
-      "prefer-spread": "off",
-      "no-prototype-builtins": "off",
-      "no-useless-escape": "off",
-      "@typescript-eslint/no-explicit-any": "off",
-      "no-console": 1
-    },
-    "ignorePatterns": ["**/templates/**", "*.test.*"]
-}

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

@@ -1,35 +0,0 @@
-# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
-# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages
-
-name: Node.js Package
-
-on:
-  release:
-    types: [created]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 22
-      - run: npm ci
-      - run: npm test
-
-  publish-npm:
-    needs: build
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      id-token: write # required for npm trusted publishing (OIDC)
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 22
-          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

package/.mocharc.json

@@ -1,3 +0,0 @@
-{
-  "loader": "ts-node/esm"
-}

package/.vscode/mcp.json

@@ -1,8 +0,0 @@
-{
-  "servers": {
-    "maka-cli": {
-      "type": "http",
-      "url": "http://localhost:5050/mcp"
-    }
-  }
-}

package/CLAUDE.md

@@ -1,239 +0,0 @@
-# CLAUDE.md
-
-This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
-
-## About
-
-Maka-CLI is a command-line scaffolding and DevOps tool for Meteor 2.x applications with React. It provides generators for creating application components and commands for building, deploying, and managing Meteor applications.
-
-## Development Commands
-
-### Build and Test
-```bash
-# Full build: compile TypeScript and copy templates/assets
-npm run build
-
-# Watch mode for development
-npm run develop
-
-# Run tests
-npm test
-
-# Lint code
-npm run lint
-```
-
-### Build Process Details
-The `npm run build` command:
-1. Removes `./bundle` directory
-2. Compiles TypeScript to `./bundle/typescript/`
-3. Runs `prep` which copies templates, README, package.json, and game JSON files
-4. Makes the executable file at `./bundle/typescript/src/exec.js` executable
-
-### Testing the CLI Locally
-After building, test the CLI:
-```bash
-./bundle/typescript/src/exec.js <command>
-```
-
-## Architecture
-
-### Three-Tier Class Hierarchy
-
-The codebase is built on a three-tier inheritance model:
-
-**1. Tool (Base Class)** - `src/tool.ts`
-- Provides shared utility services via singleton instances
-- All Commands and Generators inherit from Tool
-- Key services accessible via properties:
-  - `this.fsi` (FSI): File system operations, project path resolution
-  - `this.cfg` (CFG): Configuration management (global and project configs)
-  - `this.mpi` (MPI): Meteor package interface, proxies to Meteor CLI
-  - `this.scaffold` (Scaffold): Template processing with EJS
-  - `this.pkg` (PKG): Package.json manipulation
-  - `this.docker` (Docker): Docker operations
-  - `this.aws` (AWS): AWS infrastructure management
-- Handles parameter validation and option processing
-- Provides `validateParams()` for interactive prompting when options are missing
-
-**2. Command (Extends Tool)** - `src/command.ts`
-- Used for operational commands: `run`, `build`, `deploy`, `test`, `aws`, etc.
-- Commands form a hierarchical tree structure (commands can have sub-commands)
-- Create with: `Command.create(opts, handler, parentCommand)`
-- The root `maka` command routes to sub-commands via `processAndRunCommand()`
-- Special handling: commands prefixed with `generate:` or `g:` are routed to the generator system
-
-**3. Generator (Extends Tool)** - `src/generator.ts`
-- Used for code scaffolding: `component`, `route`, `api`, `collection`, etc.
-- Generators form a hierarchical tree (generators can have sub-generators)
-- Create with: `Generator.create(opts, handler, undoHandler, parentGenerator)`
-- Includes history tracking to `.maka/history.json` for undo functionality
-- Auto-sets `resourceNameRequired: true` unless explicitly overridden
-- `checkWhere: true` option automatically prompts for client/server/both location
-
-### Command and Generator Registration
-
-Self-registration pattern:
-- `src/maka.ts` imports `src/commands/_index.ts` and `src/generators/_index.ts`
-- These index files import all command/generator modules
-- Each module calls `.create()` which auto-registers with its parent
-- Commands register with the root `Maka` command
-- Generators register with the root `MakaGen` generator
-
-### Entry Point Flow
-
-`src/maka.ts` (entry point):
-1. Parses CLI arguments with `minimist`
-2. Camelizes option keys with `humps` (e.g., `--my-option` → `myOption`)
-3. Calls `Maka.run(args, opts)` where Maka is the root command
-
-Root command routing (`src/commands/maka.cmd.ts`):
-- Uses `processAndRunCommand()` to parse colon-delimited commands
-- Example: `"build:docker"` traverses build → docker sub-command
-- Generator syntax: `"g:route"` or `"generate:route"` routes to generator system
-- Falls back to proxying unknown commands to Meteor CLI via `mpi.maybeProxyCommandToMeteor()`
-
-### Template System
-
-Templates located in `src/templates/`:
-- Uses EJS (Embedded JavaScript) for templating
-- Processed via `this.scaffold.write({ templatePath, outputPath, data })`
-- Must be copied to bundle during build (handled by `prep` script)
-- Common data passed to templates: `name`, `className`, `fileName`, `pathPrefix`
-
-### Options and Parameter System
-
-**Option Types:**
-- `requiredOpts`: Must be provided (prompts interactively if missing)
-- `validOpts`: Allowed options with optional validation
-- Short aliases auto-generated (first letter of option name)
-- Special `env` option: auto-prompts from available project configs
-
-**NamedParam Structure:**
-```typescript
-{
-  name: string,
-  values?: string[],        // Allowed values (will prompt if invalid)
-  regex?: RegExp,           // Pattern validation
-  description?: string,     // Help text
-  boolFlag?: boolean,       // Treat as boolean
-  hidden?: boolean          // Don't show in help
-}
-```
-
-**Generator-Specific Options:**
-- `checkWhere: true` - Automatically adds and validates `--where` option (client/server/both)
-- `where` option sets `opts.appPathPrefix` to `'lib'`, `'server'`, or `'client'`
-- Resource names can include paths: `maka g:route todos/edit` → extracts dir and name
-
-### History and Undo System
-
-Generators track actions in `.maka/history.json`:
-- Max file size: 100KB (auto-prunes oldest entries)
-- Each transaction gets a UUID
-- Related actions (same transaction) are undone together
-- Undo handlers are optional (passed as 3rd param to `Generator.create()`)
-
-## Code Conventions
-
-- **ES Modules**: Uses `type: "module"` in package.json
-- **Import extensions**: Always use `.js` extension in imports (TypeScript compiles `.ts` → `.js`)
-- **Logging**: Use `Log` class methods, never `console.log`
-  - `Log.info()`, `Log.error()`, `Log.warn()`, `Log.notice()`, `Log.success()`
-  - Color mode (light/dark) read from global config
-- **Error Handling**: Use custom error classes from `src/error.ts`
-  - `UsageError`, `MustBeInProjectError`, `NoMeteorFoundError`, etc.
-- **Async/Await**: Prefer over callbacks
-- **Handler Binding**: Handlers are auto-bound to their Command/Generator instance (`this` context)
-
-## Key Patterns
-
-### Creating a Command
-```typescript
-Command.create({
-  name: 'my-command',
-  aliases: ['mc'],
-  shortDesc: 'Short description',
-  validOpts: ['option1', 'option2'],
-  mustBeInMakaProject: true,
-  examples: ['maka my-command --option1=value']
-}, async function(args, opts) {
-  // 'this' is the Command instance
-  // Access: this.fsi, this.cfg, this.mpi, etc.
-  Log.info('Executing command');
-}, parentCommand);
-```
-
-### Creating a Generator
-```typescript
-Generator.create({
-  name: 'my-generator',
-  aliases: ['mg'],
-  shortDesc: 'Generates something',
-  checkWhere: true,  // Adds --where option
-  validOpts: [],
-}, async function(args, opts) {
-  const name = opts.resourceName;
-
-  // Process template
-  await this.scaffold.write({
-    templatePath: this.fsi.pathFromProject({
-      pathParts: ['src', 'templates', 'my-template.ejs']
-    }),
-    outputPath: this.fsi.pathFromApp({
-      pathParts: [opts.appPathPrefix, 'my-file.js']
-    }),
-    data: { name }
-  });
-
-  return { success: true, message: 'Generated successfully' };
-}, undoHandler, parentGenerator);
-```
-
-### Using Scaffold for Templates
-```typescript
-await this.scaffold.write({
-  templatePath: 'path/to/template.ejs',
-  outputPath: this.fsi.pathFromApp({ pathParts: ['app', 'components', `${name}.tsx`] }),
-  data: { name, className: pascalCase(name), fileName: kebabCase(name) }
-});
-```
-
-## Project Structure
-
-```
-src/
-├── command.ts              # Command base class
-├── generator.ts            # Generator base class
-├── tool.ts                 # Tool base class
-├── maka.ts                 # Entry point
-├── exec.ts                 # Executable wrapper
-├── error.ts                # Custom error classes
-├── commands/
-│   ├── _index.ts          # Registers all commands
-│   ├── maka.cmd.ts        # Root command
-│   └── [feature]/         # Commands organized by feature
-├── generators/
-│   ├── _index.ts          # Registers all generators
-│   ├── maka.gen.ts        # Root generator
-│   └── [generator].ts     # Individual generators
-├── templates/             # EJS templates (copied to bundle)
-│   ├── meteor/
-│   ├── react/
-│   └── service/
-└── tools/                 # Utility singleton classes
-    ├── fsi/              # File system interface
-    ├── cfg/              # Config management
-    ├── mpi/              # Meteor package interface
-    ├── scaffold/         # Template scaffolding
-    ├── actions/          # Interactive prompts (@inquirer/prompts)
-    └── [others]/
-```
-
-## Important Notes
-
-- Commands ending with `.sub.cmd.ts` are sub-commands
-- Generators can be nested: `g:kit:auth:basic-meteor` traverses kit → auth → basic-meteor
-- The `generate` command is special-cased in `maka.cmd.ts` routing logic
-- All tool singletons use `getInstance()` pattern and maintain dependencies
-- Import paths must use `.js` even for `.ts` files (ESM compatibility)