@maka/maka-cli 5.123.0 → 5.123.1

package/bundle/typescript/src/commands/build/build.js

@@ -30,22 +30,22 @@ const BuildCommand = Command.create({
     aliases: ['b'],
     shortDesc: 'Build your application into the build folder.',
     mustBeInMakaProject: true,
-    description: `
-  Using Meteor's build system, create a bundle to be stored in the
-  build/ directory as a tar.gz file.
-
-  This bundle has Meteor's Dev packages removed, and can only be run
-  using NodeJS.
-
-  Use the --directory flag to output a directory instead of a tarball.
-
-  --server and --client split the build in two, so a client-only change
-  can deploy without rebuilding or restarting the server (and vice
-  versa). A --server build serves the client the moment a --client
-  build's programs/<arch> lands beside it; a --client build's program
-  directories are drop-in siblings for a --server build. --server and
-  --client cannot be combined -- omit both for the original, unsplit
-  bundle.
+    description: `
+  Using Meteor's build system, create a bundle to be stored in the
+  build/ directory as a tar.gz file.
+
+  This bundle has Meteor's Dev packages removed, and can only be run
+  using NodeJS.
+
+  Use the --directory flag to output a directory instead of a tarball.
+
+  --server and --client split the build in two, so a client-only change
+  can deploy without rebuilding or restarting the server (and vice
+  versa). A --server build serves the client the moment a --client
+  build's programs/<arch> lands beside it; a --client build's program
+  directories are drop-in siblings for a --server build. --server and
+  --client cannot be combined -- omit both for the original, unsplit
+  bundle.
   `,
     examples: [
         'maka build',

package/bundle/typescript/src/commands/build/docker.sub.cmd.js

@@ -27,15 +27,15 @@ Command.create({
         }
     ],
     shortDesc: 'Build your application into the build folder and generate a docker image.',
-    description: `
-  Build the application and a Docker image. Docker Desktop
-  or Colima (or any other docker engine) required.
-
-  Colima:
-  https://github.com/abiosoft/colima
-
-  Docker Desktop:
-  https://www.docker.com/products/docker-desktop/
+    description: `
+  Build the application and a Docker image. Docker Desktop
+  or Colima (or any other docker engine) required.
+
+  Colima:
+  https://github.com/abiosoft/colima
+
+  Docker Desktop:
+  https://www.docker.com/products/docker-desktop/
   `,
     mustBeInMakaProject: true,
     examples: [

package/bundle/typescript/src/commands/create.js

@@ -93,16 +93,16 @@ Command.create({
             description: 'Skip final confirmation prompt before scaffolding'
         }
     ],
-    description: `
-  Create a new Maka Meteor project.
-
-  Without any arguments, you will be prompted for project settings such as
-  including GraphQL, preferring React Functional or Class-based Components,
-  Typescript or Javascript, and a few others.
-
-  You can also pass in arguments to the create command to skip the prompts.
-  For example, \`maka create my-app --js=ts --theme=material\` will create a
-  new Maka Meteor project named \`my-app\` with Typescript and Material-UI.
+    description: `
+  Create a new Maka Meteor project.
+
+  Without any arguments, you will be prompted for project settings such as
+  including GraphQL, preferring React Functional or Class-based Components,
+  Typescript or Javascript, and a few others.
+
+  You can also pass in arguments to the create command to skip the prompts.
+  For example, \`maka create my-app --js=ts --theme=material\` will create a
+  new Maka Meteor project named \`my-app\` with Typescript and Material-UI.
   `,
     mustBeInMakaProject: false,
     examples: [
@@ -568,32 +568,32 @@ Command.create({
         // Create AI helper file for agents
         try {
             const aiHelperPath = path.join(projectDirectory, '.maka', 'AI_DEVELOPMENT.md');
-            const aiHelperContent = `# AI Development Guide
-
-This project is managed by **Maka-CLI**, a command-line scaffolding tool for Meteor applications.
-
-## For AI Agents
-
-### Key Concepts
-
-1. **Use \`maka\` commands** - Don't use \`meteor\` or \`npm\` directly
-2. **Commands work from anywhere** - No need to cd into the 'app' directory
-3. **Package management** - Use \`maka npm install\` and \`maka add\` for packages
-4. **Check logs after changes** - Logs are in \`.maka/logs/run-[env]-latest.log\`
-5. **Verify timestamps** - Recent logs (< 1 min) indicate the app is running
-
-### Project Structure
-
-\`\`\`
-.maka/                  # Maka configuration and metadata
-  ├── config.json       # Project settings
-  └── logs/             # Run logs with timestamps
-app/                    # Meteor application code
-\`\`\`
-
-## More Information
-
-Run \`maka --help\` or \`maka <command> --help\` for the full command reference.
+            const aiHelperContent = `# AI Development Guide
+
+This project is managed by **Maka-CLI**, a command-line scaffolding tool for Meteor applications.
+
+## For AI Agents
+
+### Key Concepts
+
+1. **Use \`maka\` commands** - Don't use \`meteor\` or \`npm\` directly
+2. **Commands work from anywhere** - No need to cd into the 'app' directory
+3. **Package management** - Use \`maka npm install\` and \`maka add\` for packages
+4. **Check logs after changes** - Logs are in \`.maka/logs/run-[env]-latest.log\`
+5. **Verify timestamps** - Recent logs (< 1 min) indicate the app is running
+
+### Project Structure
+
+\`\`\`
+.maka/                  # Maka configuration and metadata
+  ├── config.json       # Project settings
+  └── logs/             # Run logs with timestamps
+app/                    # Meteor application code
+\`\`\`
+
+## More Information
+
+Run \`maka --help\` or \`maka <command> --help\` for the full command reference.
 `;
             fs.writeFileSync(aiHelperPath, aiHelperContent);
             Log.success(`Created AI development guide: .maka/AI_DEVELOPMENT.md`);

package/bundle/typescript/src/commands/debug.js

@@ -26,10 +26,10 @@ Command.create({
     ],
     maxArgLength: 1,
     shortDesc: 'Debug your app for a given environment.',
-    description: `
-  Debug your app for a given environment. This command will source the process.env file for the given environment
-  and then run meteor debug. This allows you to debug your app in a given environment. This command will also
-  source the settings.json file for the given environment and pass it to meteor debug.
+    description: `
+  Debug your app for a given environment. This command will source the process.env file for the given environment
+  and then run meteor debug. This allows you to debug your app in a given environment. This command will also
+  source the settings.json file for the given environment and pass it to meteor debug.
   `,
     mustBeInMakaProject: true,
     examples: [

package/bundle/typescript/src/commands/deploy/deploy.command.js

@@ -7,8 +7,8 @@ const DeployCommand = Command.create({
     validOpts: [],
     mustBeInMakaProject: true,
     shortDesc: 'Deploy your application',
-    description: `
-  Deploy your app to an Ubuntu server running in AWS, On Prem,
+    description: `
+  Deploy your app to an Ubuntu server running in AWS, On Prem,
   or even ARM, or to Meteor Galaxy hosted platform.`,
     examples: [
         'maka deploy:ubuntu --env prod',

package/bundle/typescript/src/commands/deploy/galaxy.sub.cmd.js

@@ -51,8 +51,8 @@ Command.create({
     mustBeInMakaProject: true,
     requiredOpts: ['env'],
     shortDesc: 'Deploy your application',
-    description: `
-  Deploy your application to Galaxy, Meteor's hosting platform.
+    description: `
+  Deploy your application to Galaxy, Meteor's hosting platform.
   `,
     examples: [
         'maka deploy galaxy --env prod --free',

package/bundle/typescript/src/commands/deploy/github.sub.cmd.js

@@ -34,14 +34,14 @@ Command.create({
     mustBeInMakaProject: true,
     requiredOpts: ['env'],
     shortDesc: 'Scaffold a GitHub Actions CI/CD deploy pipeline',
-    description: `
-  Scaffolds a GitHub Actions workflow (.github/workflows/deploy.yaml) plus a
-  config/<env>/deploy.sh and nginx.conf, wiring up dotenvx-encrypted secrets
-  and Let's Encrypt SSL that survives every redeploy.
-
-  Requires an existing config/<env>/ssh.json (see "maka aws:create-instance"
-  and "maka aws:set-host") and a config/<env>/process.env that's already been
-  encrypted with dotenvx (see "maka env:set").
+    description: `
+  Scaffolds a GitHub Actions workflow (.github/workflows/deploy.yaml) plus a
+  config/<env>/deploy.sh and nginx.conf, wiring up dotenvx-encrypted secrets
+  and Let's Encrypt SSL that survives every redeploy.
+
+  Requires an existing config/<env>/ssh.json (see "maka aws:create-instance"
+  and "maka aws:set-host") and a config/<env>/process.env that's already been
+  encrypted with dotenvx (see "maka env:set").
   `,
     examples: [
         'maka deploy:github --env production',

package/bundle/typescript/src/commands/deploy/ubuntu.sub.cmd.js

@@ -66,8 +66,8 @@ Command.create({
     isPro: false,
     requiredOpts: ['env'],
     shortDesc: 'Deploy your application',
-    description: `
-  Deploy your app to an Ubuntu server running in AWS, On Prem,
+    description: `
+  Deploy your app to an Ubuntu server running in AWS, On Prem,
   or even ARM.`,
     examples: [
         'maka deploy:ubuntu --env prod',

package/bundle/typescript/src/commands/env/env.command.js

@@ -6,14 +6,14 @@ const EnvCommand = Command.create({
     validOpts: [],
     mustBeInMakaProject: true,
     shortDesc: 'Manage secrets in a config/<env>/process.env file',
-    description: `
-  Set or read secrets (KEY VALUE pairs) in a config/<env>/process.env file.
-
-  Values are encrypted in place with dotenvx (https://dotenvx.com) for every
-  environment except local, which stays plaintext for easy local development.
-  The encrypted process.env and its DOTENV_PUBLIC_KEY are safe to commit; the
-  sibling .env.keys file holding the private key is gitignored and must never
-  be committed.
+    description: `
+  Set or read secrets (KEY VALUE pairs) in a config/<env>/process.env file.
+
+  Values are encrypted in place with dotenvx (https://dotenvx.com) for every
+  environment except local, which stays plaintext for easy local development.
+  The encrypted process.env and its DOTENV_PUBLIC_KEY are safe to commit; the
+  sibling .env.keys file holding the private key is gitignored and must never
+  be committed.
   `,
 }, async function () {
     throw new UsageError();

package/bundle/typescript/src/commands/env/set.sub.cmd.js

@@ -15,17 +15,17 @@ Command.create({
         }
     ],
     shortDesc: 'Set one or more secrets in a config/<env>/process.env file',
-    description: `
-  Set one or more KEY VALUE pairs in a config/<env>/process.env file.
-
-  KEY and VALUE are separate arguments (not joined with "="), so quote VALUE
-  if it contains spaces, "&", "?", or other shell-special characters, e.g.
-  a MongoDB connection string with a query string:
-  maka env:set --env production MONGO_URL "mongodb+srv://user:pass@host/db?retryWrites=true&w=majority"
-
-  For every environment except local, the value is encrypted in place with
-  dotenvx -- the file's DOTENV_PUBLIC_KEY is generated on first use if it
-  doesn't already exist. local stays plaintext for easy local development.
+    description: `
+  Set one or more KEY VALUE pairs in a config/<env>/process.env file.
+
+  KEY and VALUE are separate arguments (not joined with "="), so quote VALUE
+  if it contains spaces, "&", "?", or other shell-special characters, e.g.
+  a MongoDB connection string with a query string:
+  maka env:set --env production MONGO_URL "mongodb+srv://user:pass@host/db?retryWrites=true&w=majority"
+
+  For every environment except local, the value is encrypted in place with
+  dotenvx -- the file's DOTENV_PUBLIC_KEY is generated on first use if it
+  doesn't already exist. local stays plaintext for easy local development.
   `,
     examples: [
         'maka env:set --env production MONGO_URL mongodb://localhost:27017/app',

package/bundle/typescript/src/commands/game/sideQuest/commands/go.js

@@ -323,7 +323,7 @@ export class GoCommand extends Command {
             // step aside for each other. Said out loud, because the map moves.
             const yielded = yieldDoorway(currentRoom, direction, this.actor);
             if (yielded)
-                crossNote = `${yielded} steps out of the ${direction} doorway to let you through.
+                crossNote = `${yielded} steps out of the ${direction} doorway to let you through.
 `;
             const inTheWay = doorwayFurniture(currentRoom, direction);
             if (inTheWay) {

package/bundle/typescript/src/commands/game/sideQuest/commands/search.js

@@ -93,17 +93,17 @@ function describeBarriers(room, actor) {
             // had to rediscover. One copy, one place to be right.
             const sealed = sealedRouteTo(room, actor, anchor);
             const advice = sealed ?? `Too far to work from here -- "move to ${anchor}" for a proper look.`;
-            out += `
-
-${header}
+            out += `
+
+${header}
   ${advice}`;
             continue;
         }
         const made = device.barrierSummary();
-        out += `
-
-${header}
-${device.description}${made ? `
+        out += `
+
+${header}
+${device.description}${made ? `
   ${made}` : ''}`;
         // EXACTLY WHAT TO TYPE, and it is NOT coaching -- it stands with
         // hints off. Every verb that works this device, not just the
@@ -120,13 +120,13 @@ ${device.description}${made ? `
             ...(device.code ? [`"use ${device.name.toLowerCase()} <the code>"`] : []),
             ...(device.keyItem ? [`"unlock" with ${device.keyItem.name}`] : []),
         ];
-        out += `
+        out += `
   Work it: ${ways.join(' / ')}`;
         if (device.opensExit)
             out += ` (or "${device.verbs()[0]} ${device.opensExit}")`;
         const coach = device.getHint();
         if (coach)
-            out += `
+            out += `
 ${coach}`;
     }
     return out;

package/bundle/typescript/src/commands/game/sideQuest/commands/source.js

@@ -159,13 +159,13 @@ export class SourceCommand extends Command {
         }
         if (AI.isConfigured()) {
             try {
-                const reply = await AI.ask(`You are the gear catalog of a Shadowrun text adventure. The player wants to buy: "${request}".
-Respond with ONLY a JSON object (no prose, no fences):
-{ "name": string (proper item name), "category": one of ${Object.keys(Category).join('|')},
-  "rating": one of ${Object.keys(Rating).join('|')}, "size": one of ${Object.keys(Size).join('|')},
-  "shape": string, "color": string, "texture": string, "weight": number (kg),
-  "price": integer nuyen (street price, 50-25000), "availability": integer 2-14 (higher = harder to find),
-  "description": one gritty sentence }
+                const reply = await AI.ask(`You are the gear catalog of a Shadowrun text adventure. The player wants to buy: "${request}".
+Respond with ONLY a JSON object (no prose, no fences):
+{ "name": string (proper item name), "category": one of ${Object.keys(Category).join('|')},
+  "rating": one of ${Object.keys(Rating).join('|')}, "size": one of ${Object.keys(Size).join('|')},
+  "shape": string, "color": string, "texture": string, "weight": number (kg),
+  "price": integer nuyen (street price, 50-25000), "availability": integer 2-14 (higher = harder to find),
+  "description": one gritty sentence }
 Stay true to Shadowrun 5e's sense of price and availability. If the request is not a plausible piece of gear, respond with exactly: NO`);
                 const text = (reply ?? '').trim();
                 if (!/^no$/i.test(text)) {