[stefan-ernst]

Why

vite.config.js named only milkdown/dnd/xterm, so Excalidraw, mermaid and cytoscape landed in opaque chunk-* files shared with unrelated code. A deploy that touched one of them invalidated the whole shared file, and there was no guard against them leaking into the entry.

What

• Explicit groups for excalidraw, mermaid and cytoscape, each with includeDependenciesRecursively: false. With the default, Excalidraw absorbs mermaid (a dependency of @excalidraw/mermaid-to-excalidraw) and mermaid absorbs cytoscape, producing one multi-megabyte chunk per group.
• Entry guard now also rejects mermaid and cytoscape assets in index.html.
• The app's own locales and the shiki grammars are deliberately not grouped: each is a per-file dynamic import, so one chunk per locale/language is the point (merging them would make the first switch load every one). Excalidraw's ~100 bundled locales are excluded from the group for the same reason.

Before / after

Metric	Before	After
Initial entry payload (JS+CSS in index.html)	187.1 KiB	187.1 KiB
Root shell (App-*.js, budget 50/20 KiB)	28.6 KiB raw / 11.6 KiB gzip	28.6 KiB raw / 11.6 KiB gzip
Total JS	19.69 MB	19.66 MB
Excalidraw	opaque chunk-* (1778 + 522 + 520 KB)	excalidraw-*.js (2726 KB)
Mermaid	opaque chunk-* (647 + 203 KB)	mermaid-*.js (2144 KB)
Cytoscape	cytoscape.esm-*.js (423 KB)	cytoscape-*.js (423 KB)

The entry was already small from earlier work (WI-608/610/616); this makes the lazy split explicit and cache-stable. The loaded total is unchanged.

Verification

• bun run build:app + check-entry-assets.js — pass
• bun run check, bun run typecheck — pass
• Full ../core-tests frontend suite — 437 files, 3270 tests pass
• Browser (built bundle, run-e2e.sh): pages-excalidraw.spec.ts (Excalidraw + mermaid render, 6 tests), item-description-markdown-view.spec.ts, critical-browser-page.spec.ts — pass

Pairs with Windshiftapp/core-tests-internal#34.

[github-actions]

Size Change: 0 B 🆕

Total Size: 0 B

_{compressed-size-action}