@ankhorage/ankh

中文文档
0.13.3发布于 2026/10/29MITTypeScriptES Module构建来源已验证近 30 天下载 13万

Bun-first root CLI front door for Ankhorage provider commands.

原始使用文档
文档目录3 节
  1. Usage
  2. Bootstrap status
  3. Generated documentation

@ankhorage/ankh

license: MIT npm: v0.13.3 runtime: bun typescript: strict eslint: checked prettier: checked build: checked tests: checked docs: paradox

Bun-first root CLI front door for Ankhorage provider commands.

Usage

Bootstrap status

@ankhorage/ankh is the root CLI front door and command bus for Ankhorage.

ankh --help, provider help, planning, and dispatch all resolve providers through the same dynamic discovery path. Discovery combines providers installed alongside the running Ankh CLI with the current package/workspace when present; a project-local package wins over an installed package with the same package name.

There are no hard-coded provider categories. A package becomes available through its ankh package metadata and valid provider module, and root help lists only providers resolved by that same invocation.

No domain behavior belongs in the root CLI. Domain behavior stays in provider packages such as infra, templates, studio, board, doctor, and devtools.

Root built-ins are help, planning, and version output. ankh commands is not a separate bootstrap command; the command overview belongs to root help.

ankh <category> --help and ankh <category> -h render provider-backed package help using the package description and complete command list without exposing capability or provider metadata. Provider manifests also feed the shared provider-help renderer exported by @ankhorage/ankh so standalone CLIs do not need a second hand-maintained command list.

ankh <category> <command> ...args performs basic direct dispatch to a loaded provider handler. The root CLI stays a thin router: providers own option parsing, validation, output, and behavior.

ankh plan <category> <command> asks a provider planning handler for an inspectable AnkhCommandPlan without executing provider command handlers. Use --json for stable machine-readable output.

Provider packages expose planning through optional planningHandlers on their AnkhRuntimeCommandProvider default export. Planning is a provider contract, not workflow execution: the root CLI routes to provider planning handlers and renders returned plans, but it does not compose real workflows, create projects, run commands, or execute destructive steps.

ankh run ... remains deferred until explicit execution semantics are designed.

Source: src/readme-usage.ts

import { runCli } from './cli/index.js';

await runCli(['--help']);

Generated documentation

版本与发布记录

@ankhorage/ankh 共发布 137 个版本,首次发布于 2026/07/01;过去 12 个月发布了 137 个版本。最新版本附带 npm provenance 构建来源证明,可追溯到公开的 CI 构建记录。

版本发布日期距今
0.13.3latest2026/10/297 天前
0.13.22026/10/1719 天前
0.13.12026/10/1126 天前
0.13.02026/10/1027 天前
0.12.22026/10/0829 天前
0.12.12026/10/0829 天前

关于 @ankhorage/ankh 的常见问题

@ankhorage/ankh 是什么?

Bun-first root CLI front door for Ankhorage provider commands.

如何安装 @ankhorage/ankh?

在项目目录运行 npm install @ankhorage/ankh,或使用 pnpm add / yarn add / bun add。它还提供命令行工具 ankh,可以用 npx ankh 直接运行。

@ankhorage/ankh 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@ankhorage/ankh 支持 ESM 还是 CommonJS?

以 ES Module 形式发布,推荐使用 import 引入。在 CommonJS 项目中,Node.js 20.19+ / 22.12+ 可以直接 require() 不含顶层 await 的 ES Module,更早的版本需要改用动态 import()。

@ankhorage/ankh 可以商用吗?

@ankhorage/ankh 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@ankhorage/ankh 的下载量有多少?

根据 npm 官方下载统计,@ankhorage/ankh 在 2026/10/06 – 2026/11/04 这 30 天内被下载 129,509 次,日均约 4,317 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@ankhorage/ankh 还在维护吗?

最新版本 0.13.3 发布于 2026/10/29(7 天前);至今共发布 137 个版本,其中过去 12 个月发布了 137 个;首次发布于 2026/07/01。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。