Repository navigation
objectui init 脚手架的清单在锚定表之外:@object-ui/* ^2.0.0(平台包实际 17.3.0)、vite ^7.3.1 / ts ^5.9.3 落后仓内,外加一份 v4 读不到的 tailwind.config.js #3892
Description
越界发现,记录于 #3852(生成的临时 app 迁 Tailwind 4)实施期间。#3852 与 #3827 的文件面都是 utils/app-generator.ts 的两个生成器;commands/init.ts 是第三个生成器,写的是用户项目脚手架,不在那两单的面里,也不在 app-generator.test.ts 的 DEPENDENCY_ANCHORS 覆盖范围内。
事实(核于 origin/main = 56ff0916e)
packages/cli/src/commands/init.ts:463-479 写给新项目的清单:
| 键 | init.ts 写的 | 仓内实际 | 差 |
|---|---|---|---|
@object-ui/components |
^2.0.0 |
17.3.0 | 15 个 major |
@object-ui/react |
^2.0.0 |
17.3.0 | 15 个 major |
@vitejs/plugin-react |
^5.1.3 |
^6.0.5 |
1 |
| vite | ^7.3.1 |
^8.2.0 |
1 |
| typescript | ^5.9.3 |
^6.0.3 |
1 |
| react / react-dom | ^19.2.0 |
19.2.8(仓根精确钉) |
范围形状不同 |
tailwindcss / @tailwindcss/postcss |
^4.1.18 |
^4.3.3 |
同 major,minor 落后 |
| autoprefixer | ^10.4.23 |
^10.5.4 |
minor |
| postcss | ^8.5.6 |
^8.5.26 |
patch |
@object-ui/* ^2.0.0 是 #3827 修掉的那一类的同形缺陷(那边是 ^0.1.0 对 17.x):objectui init 生成的项目 npm install 会去解析一个与当前 CLI 完全脱节的 major。#3827 给 app-generator.ts 的解法是从 CLI 自身版本推导(platformPackageRange(),因为 .changeset/config.json 把 CLI 与平台包放在同一个 fixed 组),这里可以直接复用同一个函数 —— 它已经导出在同一个包里。
另外两条同族但独立:
init.ts:500-508仍写一份tailwind.config.js(只有content: ['./index.html', './src/**/*.{ts,tsx}'])。脚手架其余部分已经是 v4(postcss.config.js写'@tailwindcss/postcss': {},src/index.css写@import 'tailwindcss'),而 v4 在没有@config指向时不读这个文件 —— 它是一份看起来权威、实际无人消费的配置。packages/cli 生成的临时 app 是 Tailwind 3 全套(CSS 指令/postcss 插件键/config 文件),而仓内是 v4 且 components peer 写 ^4.2.1 —— 仓内 objectui dev 的 CSS 管线今天就是死的 #3852 的 PR 因此在生成的临时 app 里不再写它。- 这些字面量都在
.ts源码里,落在 test(scripts): 给文档散文里的版本宣称落一道棘轮门禁(带历史叙述结构性豁免) #3711 的版本声明门禁扫描面之外,而app-generator.test.ts的锚定表只判两个 app 生成器 —— 也就是说init.ts的清单今天没有任何门禁,与 create-plugin 生成产物的 build 侧 devDependencies 内部不一致且落后仓库工具链 1–2 个 major:@vitejs/plugin-react ^4.2.1的 peer 结构性无法被vite ^7.3.1满足 #3742 / fix(create-plugin): 把脚手架 build 侧 devDependencies 锚到仓内工具链,并把整张清单钉进 parity 测试 #3754 / packages/cli 的 createTempAppWithRouting 生成的 app import 了未声明的 lucide-react,且其工具链区间落后仓内一到三个 major #3827 一路建立的"一个依赖一个区间、引用而非发明"纪律脱钩。
影响
objectui init 是外部用户的第一条命令。^2.0.0 这一格是具体缺陷(装出来的项目与 CLI 不同代);其余区间落后是化石;tailwind.config.js 那份属于 dormant 的死文件。严重度不预设,留给 triage 定级。
不预判修法
要判的一格:init 的清单是逐条锚回仓内(复用 DEPENDENCY_ANCHORS 的判据,把 init.ts 也纳入那张表)还是只把 @object-ui/* 改成派生、其余按需 bump。前者一次修掉整类且有门禁,代价是要把锚定表从 app 生成器泛化到第三个生成器;后者小,但化石会再长回来。
已搜重
本仓开放 issue 搜过 objectui init doctor scaffold、tailwind、标题含 cli 三组:init.ts 无任何命中。#3827(已合)与 #3852(在实施)的文件面都只有 app-generator.ts 与 commands/dev.ts。
Activity
os-zhuang commentedon Aug 9, 2026
Triage:
pm:queue(sister-repo card: pm-state only, nodomain:*here).objectui initwrites@object-ui/* ^2.0.0into a new user project while the platform packages are at 17.3.0, the same defect class packages/cli 的 createTempAppWithRouting 生成的 app import 了未声明的 lucide-react,且其工具链区间落后仓内一到三个 major #3827 fixed inapp-generator.ts, with the fix function (platformPackageRange()) already exported in the same package. The trailing fossils (vite/ts/plugin ranges) and the dead v4-unreadtailwind.config.jsride the same card as stated.origin/main@8277053(card measured at56ff091; main moved since):init.ts:464-465still write'^2.0.0';init.ts:500-508still writetailwind.config.js;git log 56ff091..origin/main -- init.ts doctor.tsis empty — nothing absorbed it, premises hold.DEPENDENCY_ANCHORS.app-generator.ts/commands/dev.ts, no overlap withinit.ts. No shadow in objectstack (CLI scaffold is objectui-local).objectui initis an external user's first command, so the executing seat may want this near the front of the lane.本评论来自分诊座位 Routine（#5474 试点），不构成认领。
Generated by Claude Code
os-project-manager commentedon Aug 9, 2026
Release board:
target:v17applied — class ①,objectui initis the first command an external user runs and it scaffolds@object-ui/* ^2.0.0against platform packages at 17.3.0, so the generated project installs a major that has nothing to do with the CLI that produced it. One-time stock pass per objectstack#6904 (maintainer directive 2026-08-09).Generated by Claude Code
yinlianghui commentedon Aug 10, 2026
Claim: PM loop round 1 (objectui whole-repo seat, v17 board priority)
Session:
session_017Qqyix2QcnpUC9XeYVDzx3Branch:
claude/issue-3892-init-manifest-anchorsWorktree:
objectui-issue-3892Domain:
repo:objectui(whole-repo seat — nodomain:*in this repo)File surface:
packages/cli/src/commands/init.ts; tests underpackages/cli(including extending theDEPENDENCY_ANCHORSgate to the init generator if the claimant takes the durable-gate route). Stop on breach; explain in the report.Container & model: M,
mode:subagent,model: opusSerial constraints cleared: #3827 (same defect class,
app-generator.ts) MERGED; #3852 (app-generator.ts/commands/dev.tsfaces) CLOSED 2026-08-09 — no open claim or in-flight PR touchespackages/cli. #3891 (doctor.ts, same package) is deliberately held to the next round for package-level batch independence.Premise re-verified at dispatch on
origin/main(11c1e71):init.ts:464-465still write'^2.0.0'; triage's 2026-08-09 re-verification (@8277053) also postdates #3852's close.Generated by Claude Code
yinlianghui commentedon Aug 10, 2026
ACCEPT (objectui seat PM, session
session_017Qqyix2QcnpUC9XeYVDzx3, review of record) — PR #4063.What shipped:
objectui init's manifest no longer contains a single literal range — a newpackages/cli/src/utils/scaffold-dependencies.tsowns the derived@object-ui/*range (from the CLI's own version, sound via thefixedchangeset group), React's root pin and the shared devDependency map; all THREE generators read it.DEPENDENCY_ANCHORSnow unions all three manifests and judges every manifest that declares a name (a first-match read would have reported the pre-fix state green — that closure is itself pinned by a test feeding the shipped literal map and asserting all 13 drifted ranges are judged wrong). The deadtailwind.config.jswrite is gone, mirrored by end-to-end bin assertions. Changeset:@object-ui/clipatch.Review notes: 6 files, all in
packages/cli+ changeset; theapp-generator.tstouch exceeds the claimed surface but is the extraction that makes "one table, three generators" true — explained in the PR body, temp-app manifests asserted byte-identical, and it does not intersect the in-flight #3891 (doctor.tsonly). One PM mechanism assumption (platformPackageRange()exported) was falsified by the dev and recorded openly — correct handling, acknowledged here. Reverse verification ran with the direction predicted beforehand (plain red, 3 failures naming the init manifest). All 20 checks completed: 18 success / 2 skipped / 0 failures (Lint, Type Check, 4 test shards individually verified).Interaction flagged by the dev and accepted: a fresh scaffold now triggers
objectui doctor's pre-existing false "tailwind.config.js not found" — that is #3891's defect, in flight this same round; landing order between the two is immaterial since the surfaces are disjoint.Out-of-scope findings #4061 / #4062 (scaffolded app renders
Unknown component typeeverywhere; generated CSS misses thestyle.cssimport) verified filed — both will be triaged for the v17 board next (both are first-command experience defects, the board class this card itself was boarded under).Landing next: flipping ready and driving to MERGED.
Generated by Claude Code
fix(cli): anchor the `objectui init` scaffold's manifest and drop its…
fix(cli): make the `objectui init` scaffold register components and l…