chore: Optimize vendor chunk size via Vite manualChunks - #657
Open
vedxnt-10 wants to merge 1 commit into
Open
Conversation
|
@vedxnt-10 is attempting to deploy a commit to the mayur-pagote's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #656
Description
This PR resolves the
Some chunks are larger than 800 kBwarning produced during the Vite production build by optimizing how third-party dependencies are bundled.Previously, all
node_moduleswere lumped into a single massivevendorchunk (which exceeded 2MB), significantly impacting the initial load performance of the application.Changes Made
manualChunksinvite.config.tsto explicitly split all dependencies insidenode_modulesinto their own separate chunks, based on their package names.React.lazy()andSuspensewere already implemented effectively for routing withinsrc/App.tsx, so no further dynamic imports were necessary.Verification
npm run buildsucceeds perfectly with well-distributed chunk sizes.npm run validate:componentspasses.