Disk cache for Vite that survives restarts
Built for Frontend developers using Vite with large codebases experiencing slow first page loads after server restarts..
“[declined by vitejs/vite: closed as not planned] https://github.com/vitejs/vite/issues/1207#issuecomment-753564633 Vite's current biggest performance bottlen…”
The receipts — real demand
“[declined by vitejs/vite: closed as not planned] https://github.com/vitejs/vite/issues/1207#issuecomment-753564633 Vite's current biggest performance bottleneck is first page load with large amount of modules. This is mostly caused by congestion at the browser network layer, since every module results in a full HTTP GET request on fresh server start. To improve this, we can dump the in memory transform cache to…”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
Frontend developers using Vite with large codebases who hit slow first page loads after server restarts. No search volume; the pain (Vite core team rejected the feature) suggests the demand is real but Vite maintainers chose not to support it, signaling a niche or edge case.
Competition & the opening
Vite's built-in caching and turbopack/rspack are the primary options; the gap is persistent disk cache across restarts that doesn't require workarounds or external tools.
What's hard to build
Vite's plugin API and build graph are complex; persisting cache safely without breaking incremental builds or causing stale asset bugs requires deep Vite internals knowledge. Feasibility 6/10 reflects moderate technical depth and risk of breaking builds.
Why now
Large monorepos and npm workspaces have exploded while Vite's cold-start performance remains a known limitation.
How you'd monetize
$49/year plugin license or usage-based at $0.10 per 1M cached modules