@ant-design/cli - npm Package Compare versions

Comparing version 6.3.6 to 6.3.7

data/versions.json

@@ -65,3 +65,3 @@ {
   "v6": {
-    "6.3": "6.3.6",
+    "6.3": "6.3.7",
     "6.0": "6.0.1",
@@ -68,0 +68,0 @@ "6.1": "6.1.4",

package.json

 {
   "name": "@ant-design/cli",
-  "version": "6.3.6",
+  "version": "6.3.7",
   "description": "CLI tool for querying antd knowledge and analyzing antd usage in projects",
@@ -5,0 +5,0 @@ "type": "module",

README.md

@@ -29,3 +29,3 @@ <div align="center">
 
-Code agents (Claude Code, Codex, Gemini CLI) write better antd code when they have instant access to the right API data. This CLI gives them exactly that — **every prop, token, demo, and changelog entry for antd v4 / v5 / v6**, bundled locally, queryable in milliseconds.
+Code agents (Claude Code, Codex, Gemini CLI) write better antd code when they have instant access to the right API data. This CLI gives them exactly that — **every prop, token, demo, and changelog entry for antd v3 / v4 / v5 / v6**, bundled locally, queryable in milliseconds.
 
@@ -41,3 +41,3 @@ ```bash
 - 📦 **Fully offline** — All metadata ships with the package. No network calls, no latency, no API keys.
-- 🎯 **Version-accurate** — 55+ per-minor snapshots across v4/v5/v6. Query the exact API surface of `antd@5.3.0`, not just "latest v5".
+- 🎯 **Version-accurate** — 55+ per-minor snapshots across v3/v4/v5/v6. Query the exact API surface of `antd@5.3.0`, not just "latest v5".
 - 🤖 **Agent-optimized** — `--format json` on every command. Structured errors with codes and suggestions. Clean stdout/stderr separation.
@@ -120,2 +120,3 @@ - 🌍 **Bilingual** — Every component name, description, and doc has both English and Chinese. Switch with `--lang zh`.
 antd lint ./src                     # Check deprecated APIs & best practices
+antd migrate 3 4                    # v3 → v4 migration guide
 antd migrate 4 5 --apply ./src      # Agent-ready migration prompt
@@ -355,5 +356,6 @@ ```
 
-v4→v5 covers 25+ migration steps; v5→v6 covers 30+. Each step includes component name, breaking flag, search pattern, and before/after code.
+v3→v4 covers 15+ migration steps; v4→v5 covers 25+ migration steps; v5→v6 covers 30+. Each step includes component name, breaking flag, search pattern, and before/after code.
 
 ```bash
+antd migrate 3 4                    # v3 → v4 migration
 antd migrate 4 5                    # full checklist
@@ -360,0 +362,0 @@ antd migrate 4 5 --component Select # component-specific

README.zh-CN.md

@@ -29,3 +29,3 @@ <div align="center">
 
-Code Agent（Claude Code、Codex、Gemini CLI）在拥有即时 API 数据访问能力时，能写出更好的 antd 代码。这个 CLI 正是为此而生 — **antd v4 / v5 / v6 的每个 Prop、Token、Demo 和 Changelog 条目**，本地打包，毫秒级查询。
+Code Agent（Claude Code、Codex、Gemini CLI）在拥有即时 API 数据访问能力时，能写出更好的 antd 代码。这个 CLI 正是为此而生 — **antd v3 / v4 / v5 / v6 的每个 Prop、Token、Demo 和 Changelog 条目**，本地打包，毫秒级查询。
 
@@ -41,3 +41,3 @@ ```bash
 - 📦 **完全离线** — 所有元数据随包安装，无需网络请求，无延迟，无 API Key。
-- 🎯 **版本精确** — 跨 v4/v5/v6 的 55+ 小版本快照。查询 `antd@5.3.0` 的精确 API，而非仅 "最新 v5"。
+- 🎯 **版本精确** — 跨 v3/v4/v5/v6 的 55+ 小版本快照。查询 `antd@5.3.0` 的精确 API，而非仅 "最新 v5"。
 - 🤖 **Agent 优化** — 所有命令支持 `--format json`。结构化错误码与修复建议。stdout/stderr 严格分离。
@@ -120,2 +120,3 @@ - 🌍 **双语输出** — 每个组件名、描述和文档均有中英文。通过 `--lang zh` 切换。
 antd lint ./src                     # 检查废弃 API 和最佳实践
+antd migrate 3 4                    # v3 → v4 迁移指南
 antd migrate 4 5 --apply ./src      # 生成 Agent 迁移提示
@@ -355,5 +356,6 @@ ```
 
-v4→v5 包含 25+ 迁移步骤，v5→v6 包含 30+。每个步骤包含组件名、破坏性标记、搜索正则和前后代码对比。
+v3→v4 包含 15+ 迁移步骤，v4→v5 包含 25+ 迁移步骤，v5→v6 包含 30+。每个步骤包含组件名、破坏性标记、搜索正则和前后代码对比。
 
 ```bash
+antd migrate 3 4                    # v3 → v4 迁移
 antd migrate 4 5                    # 完整迁移清单
@@ -360,0 +362,0 @@ antd migrate 4 5 --component Select # 指定组件

skills/antd/SKILL.md

@@ -18,3 +18,3 @@ ---
 
-You have access to `@ant-design/cli` — a local CLI tool with bundled antd metadata for v4/v5/v6. Use it to query component knowledge, analyze projects, and guide migrations. All data is offline, no network needed.
+You have access to `@ant-design/cli` — a local CLI tool with bundled antd metadata for v3/v4/v5/v6. Use it to query component knowledge, analyze projects, and guide migrations. All data is offline, no network needed.
 
@@ -87,7 +87,8 @@ ## Setup
 
-When the user wants to upgrade antd (e.g., v4 → v5):
+When the user wants to upgrade antd (e.g., v3 → v4 or v4 → v5):
 
 ```bash
 # Get full migration checklist
-antd migrate 4 5 --format json
+antd migrate 3 4 --format json    # v3 → v4
+antd migrate 4 5 --format json    # v4 → v5
 
@@ -251,3 +252,3 @@ # Check migration for a specific component
 1. **Always query before writing** — Don't guess antd APIs from memory. Run `antd info` first.
-2. **Match the user's version** — If the project uses antd 4.x, pass `--version 4.24.0`. The CLI auto-detects from `node_modules` if no flag is given.
+2. **Match the user's version** — If the project uses antd 3.x or 4.x, pass `--version 3.26.0` or `--version 4.24.0`. The CLI auto-detects from `node_modules` if no flag is given.
 3. **Use `--format json`** — Every command supports it. Parse the JSON output rather than regex-matching text output.
@@ -254,0 +255,0 @@ 4. **Check before suggesting migration** — Run `antd changelog <v1> <v2>` and `antd migrate` before advising on version upgrades.

No alert changes

Improved metrics

Total package byte prevSize

28893387

2.27%

Number of package files

77

1.32%

Number of lines in readme file

419

0.48%

No dependency changes