ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Vite’s dependency pre‑bundling can make or break a monorepo dev workflow. Learn when to include or exclude workspace packages, how to fine‑tune <code>optimizeDeps</code>, and avoid common pitfalls with a concrete example and practical checklist.
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'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 Vite’s esbuild‑based dependency pre‑bundling reduces browser requests, speeds up dev server start, and improves HMR—plus how to tune it safely.
When a dependency version is changed in package.json and later rolled back to a previous version, Vite’s dependency pre‑bundling lockfile ( node_modules/.vite/deps ) may retain the entry for the newer version if the file already exists and optimizeDeps.force is not set. This can leave the dev server serving bundles built against the newer dependency while th
The goal is to keep the number of JavaScript requests the browser makes during development low while avoiding an overly large pre‑bundled chunk that hurts initial load time. Vite achieves this by pre‑bundling dependencies with esbuild, but the decision of which packages to bundle depends on Vite’s heuristic for detecting side‑effects. This heuristic is docum
When configuring Vite's dependency pre‑bundling, I want to use a glob pattern such as lodash-* in optimizeDeps.include to automatically pre‑bundle all lodash submodules without listing each one individually. However, the documentation states that optimizeDeps.include accepts only exact package name strings and does not interpret glob patterns, and it does no
Goal: Achieve a deterministic development server startup where the set of pre‑bundled modules is identical for every developer who shares the same package.json, regardless of which optional dependencies happen to be installed locally. Concern: Vite’s esbuild‑based optimizeDeps step silently omits any optional dependency that cannot be resolved, does not log
vite
vitejs