CLI Tools

CLI stands for Command Line Interface. It is a way to control a program by typing text instead of clicking on icons and windows (which would be a GUI — Graphical User Interface). You type a command, press Enter, and the program executes and returns a text response. This is not specific to JavaScript or the web — ls, cd, git, curl, python, and docker are all CLIs, and they have existed long before the internet.

CLI 代表命令行界面（Command Line Interface）。这是一种通过输入文本而不是点击图标和窗口（即 GUI，图形用户界面）来控制程序的方式。你输入一条命令，按下回车键，程序就会执行并返回文本响应。这并非 JavaScript 或 Web 所特有——ls、cd、git、curl、python 和 docker 等都是 CLI，它们在互联网出现之前就已经存在了。

The anatomy of a command

Almost every terminal command follows this structure: command subcommand --flag value argument Example: git commit -m "msg" file.txt

命令的结构

几乎所有的终端命令都遵循以下结构： command subcommand --flag value argument 例如：git commit -m "msg" file.txt

Why this matters so much in development

GUIs are great for visual exploration, but CLIs win on three fronts that matter a lot for programming:

• Automation — you can put a command inside a script and run it a thousand times without clicking anything.
• Composition — as we have seen with pipes, you can combine small tools into complex workflows.
• Works without a graphical interface — servers, Docker containers, and CI/CD pipelines usually have no screen at all; you can only interact with them via the terminal.

为什么这在开发中如此重要

GUI 非常适合视觉探索，但在对编程至关重要的三个方面，CLI 具有明显优势：

• 自动化 — 你可以将命令放入脚本中，无需任何点击即可运行成千上万次。
• 组合性 — 正如我们在管道（pipes）中所见，你可以将小型工具组合成复杂的工作流。
• 无需图形界面即可运行 — 服务器、Docker 容器和 CI/CD 流水线通常根本没有屏幕；你只能通过终端与它们进行交互。

That is why practically every serious tool in the JS ecosystem (Vite, ESLint, TypeScript, Git, Docker) is, at its core, a CLI: it needs to run exactly the same way on your machine and on a remote server without any interface, in an automatable manner.

这就是为什么 JS 生态系统中几乎每一个重要的工具（Vite、ESLint、TypeScript、Git、Docker）本质上都是一个 CLI：它需要在你的机器上和没有任何界面的远程服务器上以完全相同的方式运行，并且必须是可自动化的。