@ant-design/cli 6.3.6 → 6.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ant-design/cli",
3
- "version": "6.3.6",
3
+ "version": "6.4.0",
4
4
  "description": "CLI tool for querying antd knowledge and analyzing antd usage in projects",
5
5
  "type": "module",
6
6
  "bin": {
@@ -42,19 +42,26 @@
42
42
  "publishConfig": {
43
43
  "access": "public"
44
44
  },
45
+ "overrides": {
46
+ "fast-uri": "^3.1.2",
47
+ "hono": "^4.12.18",
48
+ "ip-address": "^10.1.1"
49
+ },
45
50
  "dependencies": {
46
- "oxc-parser": "^0.123.0"
51
+ "oxc-parser": "^0.130.0"
47
52
  },
48
53
  "devDependencies": {
49
54
  "@modelcontextprotocol/sdk": "^1.29.0",
50
55
  "@types/node": "^25.5.0",
51
56
  "@vitest/coverage-v8": "^4.1.2",
52
57
  "commander": "^14.0.3",
58
+ "conf": "^15.1.0",
59
+ "env-paths": "^4.0.0",
53
60
  "envinfo": "^7.21.0",
54
61
  "gray-matter": "^4.0.3",
55
62
  "tsup": "^8.4.0",
56
63
  "tsx": "^4.19.0",
57
- "typescript": "^5.9.3",
64
+ "typescript": "^6.0.3",
58
65
  "vitest": "^4.1.2"
59
66
  }
60
67
  }
@@ -15,7 +15,7 @@ allowed-tools:
15
15
 
16
16
  # Ant Design CLI
17
17
 
18
- 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.
18
+ 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.
19
19
 
20
20
  ## Setup
21
21
 
@@ -83,11 +83,12 @@ antd doctor --format json
83
83
 
84
84
  ### 4. Migrating between versions
85
85
 
86
- When the user wants to upgrade antd (e.g., v4 → v5):
86
+ When the user wants to upgrade antd (e.g., v3 → v4 or v4 → v5):
87
87
 
88
88
  ```bash
89
89
  # Get full migration checklist
90
- antd migrate 4 5 --format json
90
+ antd migrate 3 4 --format json # v3 → v4
91
+ antd migrate 4 5 --format json # v4 → v5
91
92
 
92
93
  # Check migration for a specific component
93
94
  antd migrate 4 5 --component Select --format json
@@ -246,7 +247,7 @@ This provides 7 tools (`antd_list`, `antd_info`, `antd_doc`, `antd_demo`, `antd_
246
247
  ## Key Rules
247
248
 
248
249
  1. **Always query before writing** — Don't guess antd APIs from memory. Run `antd info` first.
249
- 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.
250
+ 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.
250
251
  3. **Use `--format json`** — Every command supports it. Parse the JSON output rather than regex-matching text output.
251
252
  4. **Check before suggesting migration** — Run `antd changelog <v1> <v2>` and `antd migrate` before advising on version upgrades.
252
253
  5. **Lint after changes** — After writing or modifying antd code, run `antd lint` on the changed files to catch deprecated or problematic usage.