Vite scaling: from a single page to a million
Horizontal scaling strategy for Vite across huge page counts and high concurrency.
Quick answer
How do I keep Vite and Rollup versions aligned?
Vite bundles a specific Rollup major version. Do not bump Rollup independently when upgrading Vite, or manualChunks behavior and the resulting split will drift.
Machine-readable page data: /data/vite-scaling.json
In-depth analysis
Vite's native-ESM dev server and Rollup-based production bundling set the baseline for modern frontend build performance and developer experience. Scaling is data-driven templates plus edge delivery — full SSG pre-render hands peak traffic to cache.
// vite.config.ts — production build, deep optimization
import { defineConfig } from 'vite';
export default defineConfig({
build: {
target: 'es2022',
cssCodeSplit: true,
rollupOptions: {
output: { manualChunks: { vendor: ['vue', 'react'] } },
},
},
});Vite Scaling · Key takeaways
- Pages driven by a single data source
- Build output fully static
- Structured data covers every page
- Edge cache load-tested
FAQ & pitfalls
How do Vite build artifacts get long-cached at the edge?
Hash-filename assets get immutable long cache; entry HTML gets must-revalidate. Changing the filename changes the URL, which naturally sidesteps cache stampedes.
Explore the hub
See all 5 guides in Traffic & SEOSame category as this article, sorted across the codebase.
AI Search scaling: from a single page to a million
Horizontal scaling strategy for AI Search across huge page counts and high concurrency.
Astro scaling: from a single page to a million
Horizontal scaling strategy for Astro across huge page counts and high concurrency.
Cloudflare Pages scaling: from a single page to a million
Horizontal scaling strategy for Cloudflare Pages across huge page counts and high concurrency.
GEO in practice: optimizing for AI search engines and LLMs
How to embed canonical Schema.org structured data so large language models and AI search engines can pick up your pages precisely.
Share & save
What readers are asking
Questions that keep coming back in reader feedback, already answered.
- 01
What goes wrong when Vite manualChunks is misconfigured?
A wrong split pushes styles into the JS bundle or creates circular dependencies, and first-paint size goes up instead of down. Start with a coarse vendor split, then refine it.
See the full guide → - 02
Why is my Astro component's interactivity not working?
Components ship as zero-JS HTML by default, so an interactive one needs a client:* directive (client:load, client:visible, …). Without it the script is never bundled into the page.
See the full guide → - 03
Why is my custom Tailwind v4 brand colour not applied?
Colours must be declared in @theme (for example --color-brand). A missing @tailwindcss/vite plugin, or a leftover v3 config, makes bg-brand silently render nothing.
See the full guide →