perf: configure manualChunks for vendor library splitting

[ali-imtiyazkhan]

Split heavy deps into separate cacheable chunks:

• vendor-three: three + @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)

Closes #3

[vercel]

@ali-imtiyazkhan is attempting to deploy a commit to the ishaanxgupta's projects Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Greptile Summary

This PR adds a manualChunks function to the Vite/Rollup build config to split heavy vendor dependencies into separate, independently-cacheable chunks. The chunk ordering is correct — more-specific patterns come first and a catch-all handles anything not explicitly named.

• Seven named vendor chunks are introduced (vendor-three, vendor-motion, vendor-charts, vendor-radix, vendor-react, vendor-query, vendor-forms) covering the heaviest dependencies, with a vendor catch-all for everything else.
• The react/ and react-dom/ patterns use a trailing slash, which correctly avoids false-positives against packages like react-hook-form or react-icons.

Confidence Score: 5/5

Safe to merge — the change is additive build config only and does not affect runtime behavior.

The manualChunks logic is well-structured: patterns are ordered from most-specific to least-specific, the trailing slash on the react/ check prevents false-positive matches, and every remaining node_modules module is covered by the catch-all. No existing functionality is touched.

No files require special attention.

Important Files Changed

Filename	Overview
vite.config.ts	Adds manualChunks to Rollup output for vendor library splitting; logic is well-ordered with a catch-all fallback; no correctness issues found

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[module id] --> B{three or react-three?}
    B -->|yes| C[vendor-three]
    B -->|no| D{framer-motion?}
    D -->|yes| E[vendor-motion]
    D -->|no| F{recharts or d3 or victory?}
    F -->|yes| G[vendor-charts]
    F -->|no| H{radix-ui?}
    H -->|yes| I[vendor-radix]
    H -->|no| J{react or react-dom?}
    J -->|yes| K[vendor-react]
    J -->|no| L{tanstack?}
    L -->|yes| M[vendor-query]
    L -->|no| N{hookform or zod?}
    N -->|yes| O[vendor-forms]
    N -->|no| P{any node_modules?}
    P -->|yes| Q[vendor catch-all]
    P -->|no| R[app code]

Loading

_{Reviews (2): Last reviewed commit: "style: add missing trailing newline to v..." | Re-trigger Greptile}

[ishaanxgupta]

LGTM!

[ishaanxgupta]

Hi @ali-imtiyazkhan this actually created a circular dependency conflict and broke Prod

[ali-imtiyazkhan]

Hi @ishaanxgupta, Thanks for catching that. I wasn't able to reproduce it locally, so I'll review PR #18 to understand the circular dependency and learn what went wrong.