ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When Vite’s production build produces unexpectedly large bundles, the culprit is often esbuild’s minification and tree‑shaking logic. This guide walks through the common causes, step‑by‑step checks, and fixes to restore lean outputs.
Learn how Vite’s esbuild‑powered pre‑bundling trims dev‑server startup time, how to tweak it with optimizeDeps, and when it might backfire.
Vite avoids slow cold starts by serving source files as native ES modules in dev and pre-bundling CommonJS dependencies on demand with esbuild. This keeps startup fast and HMR stable when configured with optimizeDeps.
Vite pre-bundles node_modules with esbuild in dev, so a stale optimized bundle is usually a cache and discovery problem — not a broken install.
Vite pre-bundles your dependencies with esbuild at dev-server startup, turning hundreds of module requests into one per package. Here's how it works, how to verify it, and when to tune optimizeDeps.
Vite pre-bundles CommonJS dependencies with esbuild at startup to serve native ES modules instantly. Learn how the cache works, how to tune optimizeDeps, and the trade-offs for dev server speed.
Vite speeds up dev server startup by pre‑bundling node_modules with esbuild, caching the result, and letting you control the process via optimizeDeps. Learn how it works, its limits, and practical checks.
Vite's dev server feels instant because esbuild pre-bundles node_modules into single-file ESM before the browser ever asks. Here's how the cache invalidates — and the monorepo case it misses.
Learn how Bun’s esbuild‑based bundler gives you instant builds for small JavaScript projects, with a concrete example, trade‑offs and next steps.
vite
vitejs
bun
javascript