πŸ“„ File detail

utils/cliArgs.ts

🧩 .tsπŸ“ 61 linesπŸ’Ύ 2,067 bytesπŸ“ text
← Back to All Files

🎯 Use case

This file lives under β€œutils/”, which covers cross-cutting helpers (shell, tempfiles, settings, messages, process input, …). On the API surface it exposes eagerParseCliFlag and extractArgsAfterDoubleDash β€” mainly functions, hooks, or classes. What the file header says: Parse a CLI flag value early, before Commander.js processes arguments. Supports both space-separated (--flag value) and equals-separated (--flag=value) syntax. This function is intended for flags that must be parsed before init() runs, such as --settings which affects configurati.

Generated from folder role, exports, dependency roots, and inline comments β€” not hand-reviewed for every path.

🧠 Inline summary

Parse a CLI flag value early, before Commander.js processes arguments. Supports both space-separated (--flag value) and equals-separated (--flag=value) syntax. This function is intended for flags that must be parsed before init() runs, such as --settings which affects configuration loading. For normal flag parsing, rely on Commander.js which handles this automatically. @param flagName The flag name including dashes (e.g., '--settings') @param argv Optional argv array to parse (defaults to process.argv) @returns The value if found, undefined otherwise

πŸ“€ Exports (heuristic)

  • eagerParseCliFlag
  • extractArgsAfterDoubleDash

πŸ–₯️ Source preview

/**
 * Parse a CLI flag value early, before Commander.js processes arguments.
 * Supports both space-separated (--flag value) and equals-separated (--flag=value) syntax.
 *
 * This function is intended for flags that must be parsed before init() runs,
 * such as --settings which affects configuration loading. For normal flag parsing,
 * rely on Commander.js which handles this automatically.
 *
 * @param flagName The flag name including dashes (e.g., '--settings')
 * @param argv Optional argv array to parse (defaults to process.argv)
 * @returns The value if found, undefined otherwise
 */
export function eagerParseCliFlag(
  flagName: string,
  argv: string[] = process.argv,
): string | undefined {
  for (let i = 0; i < argv.length; i++) {
    const arg = argv[i]
    // Handle --flag=value syntax
    if (arg?.startsWith(`${flagName}=`)) {
      return arg.slice(flagName.length + 1)
    }
    // Handle --flag value syntax
    if (arg === flagName && i + 1 < argv.length) {
      return argv[i + 1]
    }
  }
  return undefined
}

/**
 * Handle the standard Unix `--` separator convention in CLI arguments.
 *
 * When using Commander.js with `.passThroughOptions()`, the `--` separator
 * is passed through as a positional argument rather than being consumed.
 * This means when a user runs:
 *   `cmd --opt value name -- subcmd --flag arg`
 *
 * Commander parses it as:
 *   positional1 = "name", positional2 = "--", rest = ["subcmd", "--flag", "arg"]
 *
 * This function corrects the parsing by extracting the actual command from
 * the rest array when the positional is `--`.
 *
 * @param commandOrValue - The parsed positional that may be "--"
 * @param args - The remaining arguments array
 * @returns Object with corrected command and args
 */
export function extractArgsAfterDoubleDash(
  commandOrValue: string,
  args: string[] = [],
): { command: string; args: string[] } {
  if (commandOrValue === '--' && args.length > 0) {
    return {
      command: args[0]!,
      args: args.slice(1),
    }
  }
  return { command: commandOrValue, args }
}