[Auto-QA] Bundle has JS chunks over 300KB

[clubanderson]

Auto-QA [Performance]: Bundle Chunk Size

Detected: 2026-09-07T13:33:52.807Z | Focus: Performance | Commit: c888992 | Run: View

Findings

### JS chunks over 300KB
Large chunks increase initial load time — consider code splitting:
  - app-pages-D6uWH7wM.js (4.9M)
  - app-routes-b6RJU7Oz.js (1.1M)
  - cards-drasi-jI84SS9m.js (548K)
  - drei-core-vendor-z9rBPVp3.js (1016K)
  - feature-missions--pkWKXDB.js (436K)
  - msw-browser-vendor-DdZcMkuY.js (400K)
  - xterm-core-vendor-pBrHjRzb.js (332K)

### Top 10 largest bundle assets
  - app-pages-D6uWH7wM.js (4.9M)
  - app-pages-D6uWH7wM.js.gz (1.5M)
  - app-routes-b6RJU7Oz.js (1.1M)
  - drei-core-vendor-z9rBPVp3.js (1016K)
  - sqlite3-DGXXSD5r.wasm (840K)
  - app-pages-D6uWH7wM.js.br (768K)
  - cards-drasi-jI84SS9m.js (548K)
  - feature-missions--pkWKXDB.js (436K)
  - msw-browser-vendor-DdZcMkuY.js (400K)
  - index-9yFYNXmB.css (352K)

### Bundle summary
  - Total size: 24480KB
  - JS chunk count: 86

Suggested Improvements

• Split large chunks using React.lazy and dynamic imports at route level
• Use vite-bundle-visualizer or rollup-plugin-visualizer to identify what is large
• Move large third-party libs to a separate manual chunk in vite.config.ts
• Consider loading non-critical libraries on demand (e.g., chart libs)

PR Guidance: Keep changes under 50 lines (size S) for best acceptance rate. Split larger fixes into multiple PRs.

---

This issue was automatically created by the Auto-QA workflow during Performance focus day.

[github-actions]

🐝 Hi @clubanderson! I'm kubestellar-hive[bot], an automation bot for this repo.

Trusted users — org members and contributors with write access — can mention @kubestellar-hive in a comment to trigger repo automation.
On issues, that mention queues an automated fix attempt. On pull requests, it records extra context for existing automation.
This is not an interactive Q&A bot, so mentions should be treated as requests for automation rather than a conversation.

Automation may take a moment to start, and follow-up happens through workflow activity rather than chat replies.

[hivecommons-hive]

Already fixed — closing as not planned

Verified against current main (d6123ddf9a). The scan ran against commit c888992 (2026-09-07); since then web/vite.config.ts build.rolldownOptions.output.manualChunks has been extended to split every chunk named in this finding into granular sub-chunks. Each of the flagged chunks now has dedicated splitting rules (with comments citing the exact flagged sizes):

• drei-core-vendor (1016K) → split into ~15 sub-chunks: drei-shaders, drei-text3d, drei-env, drei-staging, drei-controls, drei-loaders, drei-misc, drei-materials, drei-abstractions, drei-gizmos, drei-shapes, drei-cameras, drei-helpers-core, drei-portals, drei-web, plus the residual core (vite.config.ts ~L224-241). Comment: "Split drei into sub-chunks to reduce 1012KB drei-core chunk."
• xterm-core-vendor (332K) → xterm-common, xterm-renderer, xterm-browser, xterm-headless + core (~L256-261). Comment: "Further split xterm-core by internal modules to reduce 332KB chunk."
• msw-browser-vendor (400K) → msw-interceptors, msw-browser, msw-node, msw-vendor (~L334-339).
• cards-drasi (548K) → cards-drasi-graph, cards-drasi-topology, cards-drasi-pipelines + residual (source-chunk rules). Comment: "Split the largest ... to reduce the ... chunk."
• feature-missions (436K) → dedicated feature-missions rule (~L189) that pulls components/missions, mission-control, lib/missions out of app-routes.
• app-pages (4.9M) / app-routes (1.1M) → split into app-pages, app-router, app-routes-lazy, app-routes-config, app-routes, and per-feature pages-* chunks.

All items in the finding are already resolved on main; no additional change is warranted. Re-running the scan against current main should clear this finding.

— hive: agent=scanner backend=copilot model=claude-fable-5