openxiangda 2.18.6 → 2.18.8
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/bin/distribution/launcher.js +4 -1
- package/bin/distribution/workspace.js +9 -6
- package/documentation/declarations-cheatsheet.md +1 -0
- package/documentation/getting-started.md +10 -8
- package/documentation/manifest.json +3 -3
- package/package.json +17 -16
- package/releases/2.18.8.json +31 -0
- package/skills/manifest.json +1 -1
- package/skills/openxiangda-v2/SKILL.md +4 -4
- package/skills/openxiangda-v2/references/declarations-cheatsheet.md +1 -0
- package/skills/openxiangda-v2/references/getting-started.md +10 -8
- package/releases/2.18.6.json +0 -30
|
@@ -20,7 +20,10 @@ export async function launch(packageRoot, args = process.argv.slice(2)) {
|
|
|
20
20
|
});
|
|
21
21
|
// Launcher-only updates must also work when a project's dependencies are not yet installed.
|
|
22
22
|
const launcherUpdate = args[0] === 'update' && flagValue(args, '--target') === 'launcher';
|
|
23
|
-
|
|
23
|
+
// 恢复与诊断命令(update/version/changelog)容忍钉位漂移与未安装:
|
|
24
|
+
// 否则修复命令被自己要修复的问题拦住,用户只能手写包管理器命令。
|
|
25
|
+
const recovery = launcherUpdate || ['update', 'version', 'changelog'].includes(args[0]);
|
|
26
|
+
const engine = resolveEngine(launcherUpdate ? null : workspace, packageRoot, { relaxed: recovery });
|
|
24
27
|
const context = { manifest, packageRoot, workspace, engine };
|
|
25
28
|
if (await distributionCommand(context, args)) return;
|
|
26
29
|
if (!args.length || args[0] === '--help' || args[0] === '-h') {
|
|
@@ -53,15 +53,17 @@ export function discoverWorkspace(cwd, { allowMissing = false, exact = false } =
|
|
|
53
53
|
}
|
|
54
54
|
}
|
|
55
55
|
|
|
56
|
-
export function packageEngine(packageRoot, generation, source, declaredVersion = null) {
|
|
56
|
+
export function packageEngine(packageRoot, generation, source, declaredVersion = null, { relaxed = false } = {}) {
|
|
57
57
|
packageRoot = realpathSync(packageRoot);
|
|
58
58
|
const manifest = readJson(join(packageRoot, 'package.json'));
|
|
59
59
|
const major = generation === 'v1' ? '1' : '2';
|
|
60
60
|
if (manifest.name !== 'openxiangda' || !manifest.version?.startsWith(`${major}.`)) {
|
|
61
61
|
fail('WORKSPACE_ENGINE_GENERATION_MISMATCH', `${packageRoot} 需要 ${generation} openxiangda`);
|
|
62
62
|
}
|
|
63
|
-
|
|
64
|
-
|
|
63
|
+
// relaxed:恢复与诊断命令(update/version/changelog)容忍钉位漂移——
|
|
64
|
+
// 修复命令不能被自己要修复的问题拦住。其余命令保持严格 fail-closed。
|
|
65
|
+
if (!relaxed && /^\d+\.\d+\.\d+(?:-[\w.-]+)?$/.test(declaredVersion || '') && manifest.version !== declaredVersion) {
|
|
66
|
+
fail('WORKSPACE_ENGINE_PIN_MISMATCH', `项目声明 ${declaredVersion},已安装 ${manifest.version};恢复不受本校验限制:先试 pnpm install(锁文件已指向目标版本时一步修复),钉位不一致时用 openxiangda update install --target workspace 统一升级全部声明`);
|
|
65
67
|
}
|
|
66
68
|
let entry;
|
|
67
69
|
if (generation === 'v1') {
|
|
@@ -77,15 +79,16 @@ export function packageEngine(packageRoot, generation, source, declaredVersion =
|
|
|
77
79
|
return { generation, version: manifest.version, source, packageRoot: realpathSync(packageRoot), entry, declaredVersion };
|
|
78
80
|
}
|
|
79
81
|
|
|
80
|
-
export function resolveEngine(workspace, launcherRoot) {
|
|
82
|
+
export function resolveEngine(workspace, launcherRoot, { relaxed = false } = {}) {
|
|
81
83
|
const generation = workspace?.generation || 'v2';
|
|
82
84
|
if (workspace) {
|
|
83
85
|
const manifestFile = join(workspace.root, 'package.json');
|
|
84
86
|
const manifest = existsSync(manifestFile) ? readJson(manifestFile) : {};
|
|
85
87
|
const declaredVersion = manifest.dependencies?.openxiangda || manifest.devDependencies?.openxiangda;
|
|
86
88
|
const installed = join(workspace.root, 'node_modules/openxiangda');
|
|
87
|
-
if (existsSync(join(installed, 'package.json'))) return packageEngine(installed, generation, 'workspace', declaredVersion);
|
|
88
|
-
|
|
89
|
+
if (existsSync(join(installed, 'package.json'))) return packageEngine(installed, generation, 'workspace', declaredVersion, { relaxed });
|
|
90
|
+
// relaxed 且未安装时回退启动器引擎:update install 仍可执行并完成安装。
|
|
91
|
+
if (declaredVersion && !relaxed) fail('WORKSPACE_ENGINE_NOT_INSTALLED', `${workspace.root} 已声明 openxiangda;请先按项目锁文件安装依赖,或运行 openxiangda update install --target workspace`);
|
|
89
92
|
}
|
|
90
93
|
if (generation === 'v2') return packageEngine(launcherRoot, 'v2', 'launcher');
|
|
91
94
|
let legacyManifest;
|
|
@@ -13,6 +13,7 @@
|
|
|
13
13
|
| 新建视图的 `form.fields` 必须覆盖全部无默认必填字段,或显式 `generated.create: false` | 检查器会列出缺失字段 |
|
|
14
14
|
| Workflow 详情接管的资源路由用模型级 `detailRouteCode` 表达(desktop/mobile 各引用一条 user surface 路由) | `defineDataModel({ code: 'x', detailRouteCode: { desktop: 'x-detail', mobile: 'x-detail-mobile' }, ... })` |
|
|
15
15
|
| 迁移工具/验收脚本需要看模块投影结果时,用公共出口的 `materializeApplicationModules`,不要引用 devkit 的 dist 文件路径 | `import { defineApplicationModule, materializeApplicationModules } from 'openxiangda/config';` → `const { resources } = materializeApplicationModules([module])` |
|
|
16
|
+
| system 字段(服务端赋值)可以进入查询与分组类选择(filterFields/searchableFields/sortableFields/defaultSort/sections.fields),不可进入展示与可写选择(list/form/detail.fields) | `filterFields: ['campaignId']`(system 外键筛选合法);hidden 字段任何选择都拒绝 |
|
|
16
17
|
|
|
17
18
|
## 字段声明
|
|
18
19
|
|
|
@@ -43,7 +43,9 @@ openxiangda update install --target workspace
|
|
|
43
43
|
openxiangda version --json
|
|
44
44
|
```
|
|
45
45
|
|
|
46
|
-
|
|
46
|
+
更新完成后审查依赖、锁文件差异并运行项目检查与业务验收。
|
|
47
|
+
|
|
48
|
+
升级或手改依赖后若出现 `WORKSPACE_ENGINE_PIN_MISMATCH`(项目声明与已安装版本不一致),按顺序恢复:先运行 `pnpm install`(锁文件已指向目标版本时一步修复);钉位互相不一致(多个 package.json 或锁文件各说各话)时运行 `openxiangda update install --target workspace`,它会递归统一全部声明、锁文件与安装。`update`、`version`、`changelog` 命令不受该校验限制,漂移状态下也能执行用于诊断与修复;业务命令(check/deploy/dev)保持严格 fail-closed。统一入口不会后台自动升级工具或转换项目。V1 独立 CLI 的 `update install` 会尝试刷新 V1 Skill(可用 `--no-skills` 跳过);统一入口的更新完成后按下面命令显式刷新 Skill。
|
|
47
49
|
|
|
48
50
|
### 安装或刷新 Skill
|
|
49
51
|
|
|
@@ -66,10 +68,10 @@ MCP 服务随项目根包一起安装,AI 客户端的 stdio 连接仍需配置
|
|
|
66
68
|
以下命令的版本占位符由随包资料替换为该根包的精确版本。网站源码阅读者应先确认要使用的发行版本。
|
|
67
69
|
|
|
68
70
|
```bash
|
|
69
|
-
pnpm dlx openxiangda@2.18.
|
|
70
|
-
pnpm dlx openxiangda@2.18.
|
|
71
|
-
pnpm dlx openxiangda@2.18.
|
|
72
|
-
pnpm dlx openxiangda@2.18.
|
|
71
|
+
pnpm dlx openxiangda@2.18.8 skill install --force
|
|
72
|
+
pnpm dlx openxiangda@2.18.8 auth status --base-url <平台地址> --json
|
|
73
|
+
pnpm dlx openxiangda@2.18.8 login --cwd my-app --base-url https://platform.example.com
|
|
74
|
+
pnpm dlx openxiangda@2.18.8 create my-app --base-url https://platform.example.com
|
|
73
75
|
cd my-app
|
|
74
76
|
pnpm openxiangda context --json
|
|
75
77
|
pnpm openxiangda dev
|
|
@@ -171,9 +173,9 @@ MCP 的 `docs_read` 可以读取本说明,当前没有独立的源码操作 MC
|
|
|
171
173
|
无需本地工作区,使用本 Skill 随包精确版本或已安装的对应 CLI:
|
|
172
174
|
|
|
173
175
|
```bash
|
|
174
|
-
pnpm dlx openxiangda@2.18.
|
|
175
|
-
pnpm dlx openxiangda@2.18.
|
|
176
|
-
pnpm dlx openxiangda@2.18.
|
|
176
|
+
pnpm dlx openxiangda@2.18.8 auth status --base-url <平台> --json
|
|
177
|
+
pnpm dlx openxiangda@2.18.8 source resolve <仓库URL> --base-url <平台> --json
|
|
178
|
+
pnpm dlx openxiangda@2.18.8 source clone <仓库URL> <新目录> --base-url <平台> --json
|
|
177
179
|
```
|
|
178
180
|
|
|
179
181
|
登录缺失或站点不匹配时,先按该平台执行 login。resolve 根据平台已经登记的绑定返回
|
|
@@ -1,12 +1,12 @@
|
|
|
1
1
|
{
|
|
2
2
|
"schemaVersion": "openxiangda.documentation/v1",
|
|
3
|
-
"version": "2.18.
|
|
3
|
+
"version": "2.18.8",
|
|
4
4
|
"topics": [
|
|
5
5
|
{
|
|
6
6
|
"id": "getting-started",
|
|
7
7
|
"title": "安装与开始开发",
|
|
8
8
|
"file": "getting-started.md",
|
|
9
|
-
"sha256": "
|
|
9
|
+
"sha256": "276f39b5b84d041c3ccb7a9bcd023dfcb12e83f3131724aab5dd3fbaec897b3c"
|
|
10
10
|
},
|
|
11
11
|
{
|
|
12
12
|
"id": "product-design",
|
|
@@ -48,7 +48,7 @@
|
|
|
48
48
|
"id": "declarations-cheatsheet",
|
|
49
49
|
"title": "声明速查:一次写对 config",
|
|
50
50
|
"file": "declarations-cheatsheet.md",
|
|
51
|
-
"sha256": "
|
|
51
|
+
"sha256": "5b4327eeead055b9d1f46a4122c6c2ac7052ca86e9ca2d586c8ce1b3df4d2bd2"
|
|
52
52
|
},
|
|
53
53
|
{
|
|
54
54
|
"id": "application-foundation",
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "openxiangda",
|
|
3
|
-
"version": "2.18.
|
|
3
|
+
"version": "2.18.8",
|
|
4
4
|
"description": "OpenXiangda 2.0 的统一命令、应用 SDK、MCP 与中文 AI 技能资料。",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "./dist/index.js",
|
|
@@ -60,13 +60,13 @@
|
|
|
60
60
|
"antd-mobile": "5.42.3",
|
|
61
61
|
"dayjs": "1.11.18",
|
|
62
62
|
"docx-preview": "0.3.7",
|
|
63
|
-
"openxiangda-cli": "2.4.
|
|
63
|
+
"openxiangda-cli": "2.4.16",
|
|
64
64
|
"openxiangda-contracts": "2.14.1",
|
|
65
|
-
"openxiangda-devkit-core": "2.
|
|
65
|
+
"openxiangda-devkit-core": "2.16.0",
|
|
66
66
|
"openxiangda-legacy": "npm:openxiangda@1.0.269",
|
|
67
|
-
"openxiangda-mcp": "2.0.
|
|
67
|
+
"openxiangda-mcp": "2.0.25",
|
|
68
68
|
"openxiangda-nest": "2.4.2",
|
|
69
|
-
"openxiangda-skill-kit": "2.1.
|
|
69
|
+
"openxiangda-skill-kit": "2.1.11",
|
|
70
70
|
"xlsx": "https://github.com/1377385356/openxiangda/releases/download/vendor-mirror/xlsx-0.20.3.tgz"
|
|
71
71
|
},
|
|
72
72
|
"peerDependencies": {
|
|
@@ -132,33 +132,34 @@
|
|
|
132
132
|
},
|
|
133
133
|
"openxiangdaRelease": {
|
|
134
134
|
"schemaVersion": "openxiangda.release-notes/v1",
|
|
135
|
-
"version": "2.18.
|
|
135
|
+
"version": "2.18.8",
|
|
136
136
|
"status": "reviewed",
|
|
137
|
-
"title": "OpenXiangda 2.18.
|
|
138
|
-
"summary": "
|
|
137
|
+
"title": "OpenXiangda 2.18.8:引擎钉漂移的恢复通道与确切指引",
|
|
138
|
+
"summary": "update/version/changelog 在钉位漂移或依赖未安装时仍可执行(修复命令不再被自己要修复的问题拦住);PIN_MISMATCH 错误信息给出两步恢复路径;业务命令保持严格 fail-closed。",
|
|
139
139
|
"newFeatures": [],
|
|
140
140
|
"fixes": [
|
|
141
|
-
"
|
|
142
|
-
"openxiangda
|
|
141
|
+
"统一入口对 update、version、changelog 启用宽松引擎解析:钉位漂移时可用漂移前的安装引擎执行诊断与修复;依赖未安装时回退启动器引擎,update install --target workspace 仍能完成安装并统一全部钉位。",
|
|
142
|
+
"WORKSPACE_ENGINE_PIN_MISMATCH 与 WORKSPACE_ENGINE_NOT_INSTALLED 的错误信息升级为可行动恢复指引(先 pnpm install,钉位不一致时 openxiangda update install --target workspace)。",
|
|
143
|
+
"随包文档(安装与开始开发)补充升级后漂移的恢复路径与命令豁免范围说明。"
|
|
143
144
|
],
|
|
144
145
|
"affectedUsers": [
|
|
145
|
-
"
|
|
146
|
+
"升级工具链或手改依赖后遇到引擎版本一致性校验失败的应用开发者与 AI 会话。"
|
|
146
147
|
],
|
|
147
148
|
"upgradeSteps": [
|
|
148
|
-
"应用精确依赖升级到 openxiangda 2.18.
|
|
149
|
+
"应用精确依赖升级到 openxiangda 2.18.8 后重新运行 check 与部署。"
|
|
149
150
|
],
|
|
150
151
|
"knownLimitations": [
|
|
151
|
-
"
|
|
152
|
+
"check/deploy/dev 等业务命令仍严格要求钉位一致(fail-closed 不变);自动安装未实现,恢复仍需运行一条命令。"
|
|
152
153
|
],
|
|
153
154
|
"issues": [],
|
|
154
155
|
"compatibility": {
|
|
155
156
|
"node": ">=24",
|
|
156
157
|
"workspaceGenerations": "v2",
|
|
157
158
|
"platform": "无平台配合要求。",
|
|
158
|
-
"v1": "
|
|
159
|
+
"v1": "V1 工作区同样受益于恢复命令豁免。"
|
|
159
160
|
},
|
|
160
|
-
"sha256": "
|
|
161
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.18.
|
|
161
|
+
"sha256": "6d756cf2e7f197c8c7654541a8b047309ee2e02e3060850ceefcf5f65186a9cb",
|
|
162
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.18.8"
|
|
162
163
|
},
|
|
163
164
|
"scripts": {
|
|
164
165
|
"build": "node ../../scripts/prune-package-dist.mjs && tsc -p tsconfig.json && node scripts/copy-assets.mjs",
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.18.8",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.18.8:引擎钉漂移的恢复通道与确切指引",
|
|
6
|
+
"summary": "update/version/changelog 在钉位漂移或依赖未安装时仍可执行(修复命令不再被自己要修复的问题拦住);PIN_MISMATCH 错误信息给出两步恢复路径;业务命令保持严格 fail-closed。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"统一入口对 update、version、changelog 启用宽松引擎解析:钉位漂移时可用漂移前的安装引擎执行诊断与修复;依赖未安装时回退启动器引擎,update install --target workspace 仍能完成安装并统一全部钉位。",
|
|
10
|
+
"WORKSPACE_ENGINE_PIN_MISMATCH 与 WORKSPACE_ENGINE_NOT_INSTALLED 的错误信息升级为可行动恢复指引(先 pnpm install,钉位不一致时 openxiangda update install --target workspace)。",
|
|
11
|
+
"随包文档(安装与开始开发)补充升级后漂移的恢复路径与命令豁免范围说明。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"升级工具链或手改依赖后遇到引擎版本一致性校验失败的应用开发者与 AI 会话。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"应用精确依赖升级到 openxiangda 2.18.8 后重新运行 check 与部署。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"check/deploy/dev 等业务命令仍严格要求钉位一致(fail-closed 不变);自动安装未实现,恢复仍需运行一条命令。"
|
|
21
|
+
],
|
|
22
|
+
"issues": [],
|
|
23
|
+
"compatibility": {
|
|
24
|
+
"node": ">=24",
|
|
25
|
+
"workspaceGenerations": "v2",
|
|
26
|
+
"platform": "无平台配合要求。",
|
|
27
|
+
"v1": "V1 工作区同样受益于恢复命令豁免。"
|
|
28
|
+
},
|
|
29
|
+
"sha256": "6d756cf2e7f197c8c7654541a8b047309ee2e02e3060850ceefcf5f65186a9cb",
|
|
30
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.18.8"
|
|
31
|
+
}
|
package/skills/manifest.json
CHANGED
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
{
|
|
5
5
|
"name": "openxiangda-v2",
|
|
6
6
|
"description": "使用 OpenXiangda 2.0 从模糊业务想法、已有资料或具体变更出发,通过对话发现模块、完成详细产品设计,由 AI 在工作区内调用 OpenDesign 原版 CLI/Skill/MCP 形成整体视觉与可运行原型,再开发、检查和交付应用。OpenDesign 客户端只作为可选预览器;维护 1.x 应用时使用对应的 1.x 技能。",
|
|
7
|
-
"sha256": "
|
|
7
|
+
"sha256": "b156d84ea0a5bc8c1709bf7ea831709c7396461781ac0439fbf0505eb4a0f4f5"
|
|
8
8
|
}
|
|
9
9
|
]
|
|
10
10
|
}
|
|
@@ -40,10 +40,10 @@ AI 接到新应用、页面或改版任务时,在同一个 OpenXiangda 工作
|
|
|
40
40
|
未创建工作区时使用本 Skill 随根包发布的精确版本:
|
|
41
41
|
|
|
42
42
|
```bash
|
|
43
|
-
pnpm dlx openxiangda@2.18.
|
|
44
|
-
pnpm dlx openxiangda@2.18.
|
|
45
|
-
pnpm dlx openxiangda@2.18.
|
|
46
|
-
pnpm dlx openxiangda@2.18.
|
|
43
|
+
pnpm dlx openxiangda@2.18.8 auth status --cwd <应用目录> --base-url <平台地址> --json
|
|
44
|
+
pnpm dlx openxiangda@2.18.8 login --cwd <应用目录> --base-url <平台地址>
|
|
45
|
+
pnpm dlx openxiangda@2.18.8 create <应用目录> --base-url <同一平台地址>
|
|
46
|
+
pnpm dlx openxiangda@2.18.8 skill install --force
|
|
47
47
|
```
|
|
48
48
|
|
|
49
49
|
创建前把产品要求的目标平台明确带入命令,不从旧登录态推断站点。已有工作区从原绑定恢复,平台不一致时先解决登录与目标,不改 link 文件跨站创建。
|
|
@@ -13,6 +13,7 @@
|
|
|
13
13
|
| 新建视图的 `form.fields` 必须覆盖全部无默认必填字段,或显式 `generated.create: false` | 检查器会列出缺失字段 |
|
|
14
14
|
| Workflow 详情接管的资源路由用模型级 `detailRouteCode` 表达(desktop/mobile 各引用一条 user surface 路由) | `defineDataModel({ code: 'x', detailRouteCode: { desktop: 'x-detail', mobile: 'x-detail-mobile' }, ... })` |
|
|
15
15
|
| 迁移工具/验收脚本需要看模块投影结果时,用公共出口的 `materializeApplicationModules`,不要引用 devkit 的 dist 文件路径 | `import { defineApplicationModule, materializeApplicationModules } from 'openxiangda/config';` → `const { resources } = materializeApplicationModules([module])` |
|
|
16
|
+
| system 字段(服务端赋值)可以进入查询与分组类选择(filterFields/searchableFields/sortableFields/defaultSort/sections.fields),不可进入展示与可写选择(list/form/detail.fields) | `filterFields: ['campaignId']`(system 外键筛选合法);hidden 字段任何选择都拒绝 |
|
|
16
17
|
|
|
17
18
|
## 字段声明
|
|
18
19
|
|
|
@@ -43,7 +43,9 @@ openxiangda update install --target workspace
|
|
|
43
43
|
openxiangda version --json
|
|
44
44
|
```
|
|
45
45
|
|
|
46
|
-
|
|
46
|
+
更新完成后审查依赖、锁文件差异并运行项目检查与业务验收。
|
|
47
|
+
|
|
48
|
+
升级或手改依赖后若出现 `WORKSPACE_ENGINE_PIN_MISMATCH`(项目声明与已安装版本不一致),按顺序恢复:先运行 `pnpm install`(锁文件已指向目标版本时一步修复);钉位互相不一致(多个 package.json 或锁文件各说各话)时运行 `openxiangda update install --target workspace`,它会递归统一全部声明、锁文件与安装。`update`、`version`、`changelog` 命令不受该校验限制,漂移状态下也能执行用于诊断与修复;业务命令(check/deploy/dev)保持严格 fail-closed。统一入口不会后台自动升级工具或转换项目。V1 独立 CLI 的 `update install` 会尝试刷新 V1 Skill(可用 `--no-skills` 跳过);统一入口的更新完成后按下面命令显式刷新 Skill。
|
|
47
49
|
|
|
48
50
|
### 安装或刷新 Skill
|
|
49
51
|
|
|
@@ -66,10 +68,10 @@ MCP 服务随项目根包一起安装,AI 客户端的 stdio 连接仍需配置
|
|
|
66
68
|
以下命令的版本占位符由随包资料替换为该根包的精确版本。网站源码阅读者应先确认要使用的发行版本。
|
|
67
69
|
|
|
68
70
|
```bash
|
|
69
|
-
pnpm dlx openxiangda@2.18.
|
|
70
|
-
pnpm dlx openxiangda@2.18.
|
|
71
|
-
pnpm dlx openxiangda@2.18.
|
|
72
|
-
pnpm dlx openxiangda@2.18.
|
|
71
|
+
pnpm dlx openxiangda@2.18.8 skill install --force
|
|
72
|
+
pnpm dlx openxiangda@2.18.8 auth status --base-url <平台地址> --json
|
|
73
|
+
pnpm dlx openxiangda@2.18.8 login --cwd my-app --base-url https://platform.example.com
|
|
74
|
+
pnpm dlx openxiangda@2.18.8 create my-app --base-url https://platform.example.com
|
|
73
75
|
cd my-app
|
|
74
76
|
pnpm openxiangda context --json
|
|
75
77
|
pnpm openxiangda dev
|
|
@@ -171,9 +173,9 @@ MCP 的 `docs_read` 可以读取本说明,当前没有独立的源码操作 MC
|
|
|
171
173
|
无需本地工作区,使用本 Skill 随包精确版本或已安装的对应 CLI:
|
|
172
174
|
|
|
173
175
|
```bash
|
|
174
|
-
pnpm dlx openxiangda@2.18.
|
|
175
|
-
pnpm dlx openxiangda@2.18.
|
|
176
|
-
pnpm dlx openxiangda@2.18.
|
|
176
|
+
pnpm dlx openxiangda@2.18.8 auth status --base-url <平台> --json
|
|
177
|
+
pnpm dlx openxiangda@2.18.8 source resolve <仓库URL> --base-url <平台> --json
|
|
178
|
+
pnpm dlx openxiangda@2.18.8 source clone <仓库URL> <新目录> --base-url <平台> --json
|
|
177
179
|
```
|
|
178
180
|
|
|
179
181
|
登录缺失或站点不匹配时,先按该平台执行 login。resolve 根据平台已经登记的绑定返回
|
package/releases/2.18.6.json
DELETED
|
@@ -1,30 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.18.6",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.18.6:声明速查补充模块投影出口用法",
|
|
6
|
-
"summary": "随包声明速查文档新增 materializeApplicationModules 条目:迁移工具与验收脚本从 openxiangda/config 公共出口做模块投影,不再引用 devkit dist 文件路径;文档内容随 skill-kit 分发,一并推进版本。",
|
|
7
|
-
"newFeatures": [],
|
|
8
|
-
"fixes": [
|
|
9
|
-
"声明速查(declarations-cheatsheet)模块与 CRUD 视图表新增一行:迁移/验收需要模块投影结果时使用 materializeApplicationModules 公共出口,附正确导入与调用片段。",
|
|
10
|
-
"openxiangda-skill-kit 2.1.9:声明速查内容随包同步。"
|
|
11
|
-
],
|
|
12
|
-
"affectedUsers": [
|
|
13
|
-
"从 data.resources 迁移到模块化声明的应用开发者(如数智工会 szgh-v2)与编写迁移验收脚本的维护者。"
|
|
14
|
-
],
|
|
15
|
-
"upgradeSteps": [
|
|
16
|
-
"应用精确依赖升级到 openxiangda 2.18.5 后重新运行 check 与部署。"
|
|
17
|
-
],
|
|
18
|
-
"knownLimitations": [
|
|
19
|
-
"无(本版仅随包文档变更)。"
|
|
20
|
-
],
|
|
21
|
-
"issues": [],
|
|
22
|
-
"compatibility": {
|
|
23
|
-
"node": ">=24",
|
|
24
|
-
"workspaceGenerations": "v2",
|
|
25
|
-
"platform": "无平台配合要求。",
|
|
26
|
-
"v1": "不改变 V1 运行时或应用。"
|
|
27
|
-
},
|
|
28
|
-
"sha256": "2ce270e25c679fd9cbcfc90c04ca56db386119792ffee651ac39b001ea68a39a",
|
|
29
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.18.6"
|
|
30
|
-
}
|