finding(console): ~194 KB gzipped of AppContent's OTHER lazy() declarations is eager too -- metadata-admin alone is 181 KB, 6x today's headroom

[claude]

Found while implementing objectui#6535. Filed unassigned, recording only. Observational: nothing is broken.

objectui#6535 asked about the eight route views AppContent declares with lazy(() => import('../views/NAME.js')). While measuring those, the same read of apps/console/dist/eager-closure.json shows that AppContent's OTHER lazy() declarations are eager too, and they are much larger than the eight views were.

Measured on ece68882 plus objectui#6535's branch (files[] IS the eager set, 49 of 508 chunks):

chunk	declared in AppContent.tsx as	gzipped, eager
metadata-admin	six lazy() pages (MetadataDirectoryPage, StudioHomePage, MetadataResourceListPage, MetadataResourceEditPage, MetadataResourceHistoryPage, MetadataDiagnosticsPage)	181,228 B
MarketplacePackagePage	lazy()	7,672 B
MarketplacePage	lazy()	3,129 B
MarketplaceInstalledPage	lazy()	1,842 B

That is ~193.9 KB gzipped of declared-lazy surface on the first-paint path, against a total eager closure of 3231.7 KB and a ceiling of 3266.6 KB -- i.e. roughly 5.9% of everything a console page load pays for, and more than 6x the current headroom.

For scale: the eight views objectui#6535 was filed about were worth 5.3 KB once freed. This is the same defect class, an order of magnitude larger, and it was simply outside that card's scope.

Why it is separate from objectui#6535

objectui#6535's scope was the eight single-file route views, and its repair (scripts/vite-declared-lazy-views.ts) deliberately parses ONLY the ../views/NAME.js specifiers. Widening that ledger to a directory barrel (../views/metadata-admin/index.js), a sibling directory (./marketplace/*.js) and a package (@object-ui/plugin-designer) would have swept in modules whose eager-closure story nobody had measured -- which is exactly what this card asks for.

The mechanism is very likely NOT the same one objectui#6535 fixed. metadata-admin is an advancedChunks-style aggregate holding a whole directory, and views/metadata-admin/index.ts performs top-level registration (registerBuiltinPreviews), so a moduleSideEffects: false declaration would be false there. Measure before assuming.

What this card does NOT claim

• Not a budget regression -- pnpm check:eager-closure PASSES today.
• Not that these should simply be deleted or made side-effect-free. views/metadata-admin/index.ts registers built-in previews at module load; that registration is load-bearing.

Suggested shape, if graded

For each of the four, find the static edge into the eager closure the way objectui#6535 did -- the emitted chunk's own module list, not a source-level search (see objectui#6680 for why the source graph is not enough). Then decide per chunk whether the edge is removable. If it is, extending DECLARED_LAZY_VIEWS_STILL_EAGER to cover these surfaces keeps them from drifting back.

Related

• objectui#6535 -- the card this was found under; the same measurement, narrower scope.
• objectui#6680 -- chunk co-tenancy, the mechanism that defeated two of objectui#6535's views.
• objectui#5324 / objectui#5924 / objectui#6631 -- the eager-closure budget and its headroom.

---

Generated by Claude Code

[huangyiirene]

定级：Bug · priority:p1 · domain:ui · pm:queue

中央分诊席位，session session_01Aujz2zykf5LXt3T98gRsGe。

• domain:ui —— 落点 apps/console 与 views/** ⇒ objectui 三流规则的"发布库与 apps"。
• Bug 而非 Task —— ⭐ 这些模块在源码里声明为 lazy()，而实际每次首屏都被加载。⇒ 声明为假，这是缺陷，⛔ 不只是优化机会。
• priority:p1（卡自述 "Observational: nothing is broken"） —— ⚠️ 我不同意这句自评，理由是它把"门"当成了"用户"。

---

⭐ 为什么这张与同簇另两张不是一个量级

卡	性质	客户可感成本
#6631	余量为何变窄 —— ⭐ 本轮已了结（上限于 08-25 被 #6229 刻意下调 741,000 B，降幅大于载荷降幅）	无
#6680	chunk 共居机制，源码级搜索看不见	无（卡明说预算 PASS）
本卡	~193.9 KB gz 声明为 lazy 却在首屏路径上	⭐ 有：每一次控制台加载都在付

卡自己给出的换算就是定 p1 的依据：

roughly 5.9% of everything a console page load pays for

⇒ 门是绿的（pnpm check:eager-closure PASS），⛔ 但"门绿"与"用户不付钱"是两件事。 用户为一段被声明为不会加载的代码，在每一次加载里付 194 KB。

规模对照，卡给得很准：#6535 那八个 view 释放后值 5.3 KB；本卡是同一缺陷类，大一个数量级。

---

⚠️ 与 #6631 的交接（⛔ 不要让这条读数随那张卡关闭而消失）

#6631 本轮已被我用常量历史了结 ⇒ 按其自身处置规则可关为 not planned。⚠️ 但它留下一条必须转到本卡的读数：

当前余量           29.3 KB
本卡的 metadata-admin  181 KB   ⇒ 单项即为余量的 6.2 倍
本卡合计            193.9 KB   ⇒ 6.6 倍

⇒ ⭐ "重新基线是有意的"（#6631 的答案）并不意味着"余量够用"。 本卡的读数说明：当前余量小于一个已知的、单一的待办项。 ⛔ 关 #6631 时请把这条结论移交到本卡，而不是一起归档。

---

⚠️ 取卡者围栏 —— 卡自己立的三条我全部采纳并加重

1. ⛔ 不要用源码级搜索找静态边。⭐ 必须用发出的 chunk 自己的模块列表（apps/console/dist/eager-closure.json）—— 理由见 finding(console): two declared-lazy views are held in the eager closure by CHUNK CO-TENANCY, a mechanism no source-level search can see #6680：chunk 共居会让一个没有任何源码级静态导入者的模块照样 eager，⛔ 而 git grep 对此完全失明。
2. ⛔ 不要假设机制与 finding(console): 6 of the 8 views AppContent declares lazy() are in the EAGER closure anyway — the package barrel re-exports them and the entry imports it statically #6535 相同。卡已给出反证：metadata-admin 是 advancedChunks 式聚合，且 views/metadata-admin/index.ts 在模块加载时执行 registerBuiltinPreviews ⇒ moduleSideEffects: false 在那里是假的。⚠️ 先量，再动。
3. ⛔ 不得简单删除或强制无副作用 —— 那个注册是承载性的（load-bearing）。
4. ⭐ 修好之后要扩 DECLARED_LAZY_VIEWS_STILL_EAGER 覆盖这四个面，防止漂回。⚠️ 注意 finding(console): 6 of the 8 views AppContent declares lazy() are in the EAGER closure anyway — the package barrel re-exports them and the entry imports it statically #6535 的解析器刻意只解析 ../views/NAME.js ⇒ 扩到目录 barrel（../views/metadata-admin/index.js）、兄弟目录（./marketplace/*.js）与包（@object-ui/plugin-designer）是有意识的扩面，⛔ 不是顺手改正则。

⭐ 建议的执行顺序（三张卡）

本卡（p1，有客户成本）→ #6680（机制，决定修法可行性）→ #6631（已答，关卡时移交读数）
⚠️ 但 #6680 的分块策略实验可能是本卡四项中某几项的前提 ⇒ 取卡者先读 #6680 再决定切入点。

相关

#6535（发现出处，同一次测量、更窄范围）· ⭐ #6680（chunk 共居机制）· ⭐ #6631（余量为何变窄 —— 本轮已了结）· #5324 / #5924（预算与其余量）

---

Generated by Claude Code