This repository was archived by the owner on Mar 19, 2026. It is now read-only.
Merged
Conversation
sapphi-red
commented
Dec 1, 2025
Comment on lines
-215
to
-234
| In the future, we will also introduce a "Full Bundle Mode" for Vite, which will serve bundled files in production _and development mode_. | ||
|
|
||
| ### Why introducing a Full Bundle Mode? | ||
|
|
||
| Vite is known for its unbundled dev server approach, which is a main reason for Vite's speed and popularity when it was first introduced. This approach was initially an experiment to see just how far we could push the boundaries of development server performance without traditional bundling. | ||
|
|
||
| However, as projects scale in size and complexity, two main challenges have emerged: | ||
|
|
||
| 1. **Development/Production inconsistency**: The unbundled JavaScript served in development versus the bundled production build creates different runtime behaviors. This can lead to issues that only manifest in production, making debugging more difficult. | ||
|
|
||
| 2. **Performance degradation during development**: The unbundled approach results in each module being fetched separately, which creates a large number of network requests. While this has _no impact in production_, it causes significant overhead during dev server startup and when refreshing the page in development. The impact is especially noticeable in large applications where hundreds or even thousands of separate requests must be processed. These bottlenecks become even more severe when developers use network proxy, resulting in slower refresh times and degraded developer experience. | ||
|
|
||
| With the Rolldown integration, we have an opportunity to unify the development and production experiences while maintaining Vite's signature performance. A Full Bundle Mode would allow serving bundled files not only in production but also during development, combining the best of both worlds: | ||
|
|
||
| - Fast startup times even for large applications | ||
| - Consistent behavior between development and production | ||
| - Reduced network overhead on page refreshes | ||
| - Maintained efficient HMR on top of ESM output | ||
|
|
||
| When the Full Bundle Mode is introduced, it will be an opt-in feature at first. Similar to the Rolldown integration, we are aiming to make it the default after gathering feedback and ensuring stability. |
Member
Author
There was a problem hiding this comment.
Do we want to put this somewhere?
Other than this section, it should be covered by existing docs or by content added in #529.
Member
There was a problem hiding this comment.
I hope we can write a bit about it in the Vite 8 beta blog post. More in-depth is fine when FBM actually is available (as we need docs for it then anyway)
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Removed rolldown page and added a redirect to v7 docs rolldown page.