Building Command-Line Applications

Command-line tools receive arguments through process.argv, not browser forms. The first entries normally identify the runtime and script; application arguments begin at index 2. Validate flags and show usage feedback rather than treating every input as trusted.

The parser is tested with supplied arrays for deterministic output. The real argv variable is an array of strings; pass argv.slice(2) into parseCommand in an actual CLI entry point.

Avoid assuming argv[2] exists. Commands need missing-argument handling and exit-status conventions.

Save as building-command-line-applications.ts. The following program passed strict TypeScript compilation, and the displayed output was captured by executing its emitted JavaScript with Node.js 22.16.0.

TypeScript source

import { argv } from "node:process";
function parseCommand(args: string[]): string {
  const name = args[0] ?? "world";
  return `Hello, ${name}!`;
}
console.log(parseCommand(["Maya"]));
console.log(parseCommand([]));
console.log(`Args are an array: ${Array.isArray(argv)}`);

Verified output

Hello, Maya!
Hello, world!
Args are an array: true

Compile: npx tsc --strict --target es2022 --module commonjs building-command-line-applications.ts; run: node building-command-line-applications.js. For Node.js API examples, install @types/node first. For browser projects, use the browser-specific instructions below.

The example runs in Node.js 22.16.0; if it reads runtime environment details, your displayed values may differ.

The parser is tested with supplied arrays for deterministic output. The real argv variable is an array of strings; pass argv.slice(2) into parseCommand in an actual CLI entry point.

Predict what changes if you alter one input. Then run the code to compare your reasoning with the real output.

Avoid assuming argv[2] exists. Commands need missing-argument handling and exit-status conventions.

Identify whether the failure is a type-checking issue, a configuration issue, or a runtime behavior issue before choosing a fix.

Implement --upper to uppercase the greeting and --help to explain the supported flags.

Write down your expected result first. For configuration examples, compare compiler output and diagnostics; for test examples, make the assertion fail deliberately to verify that the tool reports it.

Command-line tools receive arguments through process.

Run the primary example, then complete the practice task or environment-specific lab.