Vite best practices: engineering conventions for production
Field-tested Vite practices from production, avoiding the common anti-patterns.
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-best-practices.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. Production engineering conventions revolve around "single source of truth + explicit boundaries", steering clear of the common anti-patterns.
// 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 Best Practices · Key takeaways
- Config centralized in a single source
- CI uses --frozen-lockfile
- Secrets are placeholders, never real values in code
- Docs and code live in separate places
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 Hands-onSame category as this article, sorted across the codebase.
Astro best practices: engineering conventions for production
Field-tested Astro practices from production, avoiding the common anti-patterns.
Astro deployment guide: zero-ops edge publishing with Cloudflare Pages
Git-driven Astro deployment in practice: commit to build, atomic publish to every edge node.
Astro performance tuning: push first paint and edge response to the limit
Around Astro's real bottlenecks, an actionable LCP / INP / CLS checklist.
Astro hands-on tutorial: from zero to your first runnable project
Step-by-step walkthrough of Astro with copy-paste commands, directory layout, and a first runnable artifact.
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 →