@maka/maka-cli 5.3.0 → 5.3.2

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,54 +0,0 @@
-# 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:
-    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
-      - 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/.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)

package/eslint.config.js

@@ -1,28 +0,0 @@
-import globals from "globals";
-import pluginJs from "@eslint/js";
-import tseslint from "typescript-eslint";
-
-
-export default [
-  {files: ["**/*.{js,mjs,cjs,ts}"]},
-  {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: "^_",
-      }],
-    },
-  },
-  {
-    ignores: ["src/templates/**/*"]
-  }
-];

package/jest.config.js

@@ -1,12 +0,0 @@
-export default {
-  preset: 'ts-jest',
-  testEnvironment: 'node',
-  testMatch: ['**/*.test.ts'],
-  moduleFileExtensions: ['ts', 'js'],
-  transform: {
-    '^.+\\.ts$': 'ts-jest',
-  },
-  coveragePathIgnorePatterns: ['/bundle'],
-  passWithNoTests: true,
-};
-

package/test/integration/default.test.js

@@ -1,84 +0,0 @@
-var assert = require("chai").assert;
-var helpers = require('./integration_helpers');
-
-describe("default languages", function() {
-
-  it('react genenerated correctly', function(done) {
-    helpers.compare('react', [''], function(err) {
-      assert(err == null, err);
-      done();
-    });
-  });
-
-  it('react-material genenerated correctly', function(done) {
-    helpers.compare('react', ['--theme=material'], function(err) {
-      assert(err == null, err);
-      done();
-    });
-  });
-
-  it('react-ssr genenerated correctly', function(done) {
-    helpers.compare('react', ['--ssr=true'], function(err) {
-      assert(err == null, err);
-      done();
-    });
-  });
-
-
-  it('react-apollo genenerated correctly', function(done) {
-    helpers.compare('react', ['--graphql=apollo'], function(err) {
-      assert(err == null, err);
-      done();
-    });
-  });
-
-  it('react-apollo-ssr genenerated correctly', function(done) {
-    helpers.compare('react', ['--graphql=apollo', '--ssr=true'], function(err) {
-      assert(err == null, err);
-      done();
-    });
-  });
-
-  it('reflux genenerated correctly', function(done) {
-    helpers.compare('react', ['--client=reflux'], function(err) {
-      assert(err == null, err);
-      done();
-    });
-  });
-
-  it('reflux-material genenerated correctly', function(done) {
-    helpers.compare('react', ['--client=reflux', '--theme=material'], function(err) {
-      assert(err == null, err);
-      done();
-    });
-  });
-
-  it('reflux-ssr genenerated correctly', function(done) {
-    helpers.compare('react', ['--client=reflux', '--ssr=true'], function(err) {
-      assert(err == null, err);
-      done();
-    });
-  });
-
-  it('reflux-apollo genenerated correctly', function(done) {
-    helpers.compare('react', ['--client=reflux', '--graphql=apollo'], function(err) {
-      assert(err == null, err);
-      done();
-    });
-  });
-
-  it('reflux-apollo-ssr genenerated correctly', function(done) {
-    helpers.compare('react', ['--client=reflux', '--graphql=apollo', '-ssr=true'], function(err) {
-      assert(err == null, err);
-      done();
-    });
-  });
-
-
-  it('blaze genenerated correctly', function(done) {
-    helpers.compare('react', ['--client=blaze'], function(err) {
-      assert(err == null, err);
-      done();
-    });
-  });
-});

package/test/integration/fixtures/blaze/.maka/config.json

@@ -1,30 +0,0 @@
-{
-  "engines": {
-    "html": "html",
-    "js": "js",
-    "css": "css",
-    "api": "none",
-    "client": "blaze",
-    "test": "none",
-    "graphql": "none",
-    "ssr": "false"
-  },
-
-  "template": {
-    "html": "true",
-    "js": "true",
-    "css": "true",
-    "test": "true"
-  },
-  "features": {
-    "withTracker": "true"
-  },
-  "route": {
-    "controller": "",
-    "template": "true"
-  },
-
-  "generator": {
-    "comments": "true"
-  }
-}

package/test/integration/fixtures/blaze/.tern-project

@@ -1,17 +0,0 @@
-{
-    "libs": [
-        "browser",
-        "jquery",
-        "underscore"
-    ],
-    "loadEagerly": [ "*.js", "*/*.js", "*/*/*.js", "*/*/*/*.js" ],
-    "dontLoad": [ ".meteor" ],
-    "plugins": {
-        "meteor": {}
-    },
-    "requirejs": {
-        "baseURL": "./",
-        "paths": {}
-    },
-    "node": {}
-}

package/test/integration/fixtures/blaze/app/.meteor/.finished-upgraders

@@ -1,17 +0,0 @@
-# This file contains information which helps Meteor properly upgrade your
-# app when you run 'meteor update'. You should check it into version control
-# with your project.
-
-notices-for-0.9.0
-notices-for-0.9.1
-0.9.4-platform-file
-notices-for-facebook-graph-api-2
-1.2.0-standard-minifiers-package
-1.2.0-meteor-platform-split
-1.2.0-cordova-changes
-1.2.0-breaking-changes
-1.3.0-split-minifiers-package
-1.4.0-remove-old-dev-bundle-link
-1.4.1-add-shell-server-package
-1.4.3-split-account-service-packages
-1.5-add-dynamic-import-package

package/test/integration/fixtures/blaze/app/.meteor/.id

@@ -1,7 +0,0 @@
-# This file contains a token that is unique to your project.
-# Check it into your repository along with the rest of this directory.
-# It can be used for purposes such as:
-#   - ensuring you don't accidentally deploy one app on top of another
-#   - providing package authors with aggregated statistics
-
-y8p9ecjug4zu.hb4hpnxnc5o7

package/test/integration/fixtures/blaze/app/.meteor/packages

@@ -1,21 +0,0 @@
-# Meteor packages used by this project, one per line.
-# Check this file (and the other files in this directory) into your repository.
-#
-# 'meteor add' and 'meteor remove' will edit this file for you,
-# but you can also edit it by hand.
-
-meteor-base@1.3.0             # Packages every Meteor app needs to have
-mobile-experience@1.0.5       # Packages for a great mobile UX
-mongo@1.4.2                   # The database Meteor supports right now
-blaze-html-templates@1.0.4 # Compile .html files into Meteor Blaze views
-reactive-var@1.0.11            # Reactive variable for tracker
-tracker@1.1.3                 # Meteor's client-side reactive programming library
-
-standard-minifier-css@1.4.0   # CSS minifier run for production mode
-standard-minifier-js@2.3.1    # JS minifier run for production mode
-es5-shim@4.7.0                # ECMAScript 5 compatibility for older browsers
-ecmascript@0.10.0              # Enable ECMAScript2015+ syntax in app code
-shell-server@0.3.1            # Server-side component of the `meteor shell` command
-
-autopublish@1.0.7             # Publish all data to the clients (for prototyping)
-insecure@1.0.7                # Allow all DB writes from clients (for prototyping)

package/test/integration/fixtures/blaze/app/.meteor/platforms

@@ -1,2 +0,0 @@
-server
-browser

package/test/integration/fixtures/blaze/app/.meteor/release

@@ -1 +0,0 @@
-METEOR@1.6.1

package/test/integration/fixtures/blaze/app/.meteor/versions

@@ -1,78 +0,0 @@
-allow-deny@1.1.0
-autopublish@1.0.7
-autoupdate@1.4.0
-babel-compiler@7.0.5
-babel-runtime@1.2.2
-base64@1.0.11
-binary-heap@1.0.10
-blaze@2.3.2
-blaze-html-templates@1.1.2
-blaze-tools@1.0.10
-boilerplate-generator@1.4.0
-caching-compiler@1.1.11
-caching-html-compiler@1.1.2
-callback-hook@1.1.0
-check@1.3.1
-ddp@1.4.0
-ddp-client@2.3.2
-ddp-common@1.4.0
-ddp-server@2.1.2
-deps@1.0.12
-diff-sequence@1.1.0
-dynamic-import@0.3.0
-ecmascript@0.10.5
-ecmascript-runtime@0.5.0
-ecmascript-runtime-client@0.6.2
-ecmascript-runtime-server@0.5.0
-ejson@1.1.0
-es5-shim@4.7.3
-geojson-utils@1.0.10
-hot-code-push@1.0.4
-html-tools@1.0.11
-htmljs@1.0.11
-http@1.4.0
-id-map@1.1.0
-insecure@1.0.7
-jquery@1.11.11
-launch-screen@1.1.1
-livedata@1.0.18
-logging@1.1.20
-meteor@1.8.6
-meteor-base@1.3.0
-minifier-css@1.3.1
-minifier-js@2.3.3
-minimongo@1.4.3
-mobile-experience@1.0.5
-mobile-status-bar@1.0.14
-modules@0.11.5
-modules-runtime@0.9.2
-mongo@1.4.5
-mongo-dev-server@1.1.0
-mongo-id@1.0.7
-npm-mongo@2.2.34
-observe-sequence@1.0.16
-ordered-dict@1.1.0
-promise@0.10.2
-random@1.1.0
-reactive-var@1.0.11
-reload@1.2.0
-retry@1.1.0
-routepolicy@1.0.13
-server-render@0.3.0
-shell-server@0.3.1
-shim-common@0.1.0
-socket-stream-client@0.1.0
-spacebars@1.0.15
-spacebars-compiler@1.1.3
-standard-minifier-css@1.4.1
-standard-minifier-js@2.3.2
-templating@1.3.2
-templating-compiler@1.3.3
-templating-runtime@1.3.2
-templating-tools@1.1.2
-tracker@1.1.3
-ui@1.0.13
-underscore@1.0.10
-url@1.2.0
-webapp@1.5.0
-webapp-hashing@1.0.9

package/test/integration/fixtures/blaze/app/client/body.html

@@ -1,2 +0,0 @@
-<body>
-</body>

package/test/integration/fixtures/blaze/app/client/head.html

@@ -1,8 +0,0 @@
-<head>
-  <meta charset="utf-8">
-  <meta http-equiv="X-UA-Compatible" content="IE=edge">
-  <meta name="viewport" content="width=device-width, initial-scale=1">
-  <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->
-  <meta name="description" content="blaze">
-  <title>blaze</title>
-</head>

package/test/integration/fixtures/blaze/app/client/main.js

@@ -1 +0,0 @@
-import '/imports/startup/client';