Good first issue: reduce the frontend bundle size

[forthfate]

Summary

The production frontend build succeeds, but Vite reports that the main JavaScript bundle is larger than 500 kB after minification.

(!) Some chunks are larger than 500 kB after minification.

This is a good first issue for contributors who want to learn how the React/Vite frontend is organized.

Goal

Reduce the initial JavaScript bundle size by splitting code that is not needed for the first screen.

Suggested starting points

• Inspect the Vite build output with a bundle visualizer or Vite's chunk reporting.
• Consider lazy-loading page-level features such as the evaluation, improvement, asset-editor, or chat UI.
• Consider separating large editor or visualization dependencies into dedicated chunks.
• Keep the existing navigation and loading behavior usable while a lazily loaded page is fetched.

Acceptance criteria

• pnpm --filter agent-improvement-console-ui run build succeeds.
• The initial bundle is materially smaller, or large dependencies are placed in clearly separated lazy-loaded chunks.
• Navigation still works for every page.
• No new console errors are introduced.
• Add a short note to the PR explaining the chosen split points and the before/after build output.

Helpful commands

pnpm --filter agent-improvement-console-ui run build
pnpm --filter agent-improvement-console-ui run lint

Questions are welcome—please comment on this issue before making a large architectural change.

[KavinamuthanGP]

Hi! I'd like to work on this issue. I'll first inspect the current Vite build output and identify the largest dependencies/chunks, then make a focused code-splitting/lazy-loading change while keeping navigation and loading behavior intact. I'll include before/after build output in the PR. Thanks!

[forthfate]

Hi! Thanks for jumping in. That plan sounds solid—feel free to go ahead and assign yourself or let me know if you need help getting started. Looking forward to the PR!

[KavinamuthanGP]

Thanks! I’d be happy to work on this. I don’t seem to have the option to assign myself from the issue page. Could you please assign the issue to me?

Also, sorry for the late participation, and thanks for your patience! I’m looking forward to getting started.

[forthfate]

Hi @KavinamuthanGP , I've assigned this issue to you! Feel free to work on it at your own pace. Thanks again for your interest in this project, and I'm looking forward to working with you!

[lukitadproxd-netizen]

Your acceptance criteria are nicely bounded: reduce the initial Vite bundle, keep navigation/loading usable, and report before/after output. I can audit the current chunk report, lazy-load the page-level React features that are not needed on first screen, and add a focused smoke check for navigation. Fixed-scope starting price is USD 80, with payment by PayPal, bank transfer, Stripe/escrow, or crypto by agreement. If you want a contributor rather than a paid implementation, please confirm the preferred split points before I open a PR.

[forthfate]

Hi @lukitadproxd-netizen,

Thanks for your interest, but this issue has already been assigned to another contributor (@KavinamuthanGP) and is currently in progress.

Also, please note that this is an open-source project driven by community contributions, not paid/bountied work. Thanks!

[lukitadproxd-netizen]

Thanks for clarifying. I will not duplicate the assigned contributor's work or treat this OSS issue as paid. Withdrawing cleanly; if you later need a separate paid frontend/QA slice, the catalog is available at https://github.com/lukitadproxd-netizen/lucas-dev-services.