[Perf] Configure Vite manualChunks for vendor libraries

[ishaanxgupta]

The Vite config does not define manualChunks, meaning heavy dependencies like Three.js (~150 KB), framer-motion (~50 KB), and recharts are bundled together. This creates a monolithic vendor chunk that invalidates cache on every small application change.

Code Reference
xmem-landing/vite.config.ts

Proposed Fix
Update rollupOptions.output.manualChunks in the Vite config to split large dependencies (three, motion, radix UI) into their own cacheable vendor chunks

[ali-imtiyazkhan]

Hi @ishaanxgupta! I've worked on this issue and submitted a fix in PR #16.

Problem
The Vite config had no manualChunks defined, so Rollup was bundling all node_modules into a single monolithic vendor chunk. Every small app change busted the cache for the entire bundle — including heavy deps like Three.js, Framer Motion, and Recharts that hadn't changed at all.

What was done
Added rollupOptions.output.manualChunks in vite.config.ts to split dependencies into separate cacheable chunks:

• vendor-three — three.js + @react-three/fiber + @react-three/drei (~500 KB)
• vendor-motion — framer-motion (~50 KB)
• vendor-charts — recharts + d3-* (~80 KB)
• vendor-radix — all 25 @radix-ui/* packages (~120 KB)
• vendor-react — react + react-dom (~45 KB)
• vendor-query — @tanstack/react-query (~30 KB)
• vendor-forms — react-hook-form + zod (~25 KB)
  All vendor chunks are served from the browser cache on repeat visits.

Please review PR #16 when you get a chance. Happy to make any changes based on your feedback!