ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #vitejs
Context Vite’s dev‑server proxy accepts an object mapping request paths to options. The documented rewrite function transforms the incoming URL before forwarding, whereas the legacy pathRewrite option is no longer supported. In addition, the official docs only illustrate a static string for the target property, leaving the possibility of a dynamic target fun
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