Vite 4.0 cache directory retention limits

Question

Cache retention behavior in Vite 4.0
Vite stores compiled module artifacts under node_modules/.vite to accelerate subsequent dev‑server starts. The cache is keyed by the project’s Vite configuration, the Vite version, and a hash of each module’s source. When the dev server restarts, Vite scans the cache and rebuilds only modules whose source hash has changed.
However, the cache is never automatically pruned. After a long period of inactivity, unused entries can accumulate, consuming disk space and potentially leading to cache corruption if node_modules is modified outside Vite. The current design does not expose a configuration option to clean or prune stale entries, nor does it define a time‑based threshold for determining staleness.
Given these constraints, the following questions remain unresolved:

Does Vite 4.0 provide any mechanism to automatically prune unused cache entries after a defined period of inactivity?
What criteria would Vite use to determine that a cache entry is stale, and can this threshold be configured?
How does the absence of automatic pruning affect build performance in large projects over time?

Tasadduq Burney · Answer

Vite 4.0 does not provide a native mechanism to automatically prune unused cache entries after a defined period of inactivity. The cache located in node_modules/.vite is persistent until it is either overwritten by a new dependency build or manually deleted by the user.

How the Vite Cache Works
Vite uses a hash-based validation strategy rather than a time-based one. When the dev server starts, it performs a dependency pre-bundling phase. The validity of the cached artifacts depends on three primary factors:

Vite Configuration: Changes to vite.config.js typically invalidate the cache.
  Vite Version: Upgrading Vite triggers a cache rebuild to ensure compatibility.
  Module Source Hash: If the source code of a dependency changes, the hash changes, and Vite rebuilds only that specific module.

Because there is no 'time-to-live' (TTL) or 'last accessed' timestamp associated with individual cache entries, an entry that hasn't been used in months will remain on disk indefinitely as long as the source hash remains valid.

Performance and Disk Space Implications
The absence of automatic pruning has two main effects on large-scale projects:

Disk Bloat: In projects with frequent dependency switching or version updates, node_modules/.vite can grow significantly as old versions of bundled dependencies are never removed.
  Scan Overhead: Vite must scan the cache directory to verify hashes. While modern file systems handle large directories quickly, a massive cache containing thousands of stale files can marginally increase the initial 'cold start' time of the dev server.

Manual Cache Management
Since there is no configuration-based threshold to determine staleness, developers must manage the cache manually. If you suspect cache corruption or need to reclaim disk space, the standard approach is to remove the Vite folder manually:
# Remove only the Vite cache to force a fresh rebuild
rm -rf node_modules/.vite

To verify if your cache is being utilized, you can run Vite with the --force flag, which bypasses the existing cache and performs a full re-bundle:
npx vite --force

Vite 4.0 cache directory retention limits

Cache retention behavior in Vite 4.0

1 answer

Vite 4.0 does not provide a native mechanism to automatically prune unused cache entries after a defined period of inactivity. The cache located in `node_modules/.vite` is persistent until it is either overwritten by a new dependency build or manually deleted by the user.

How the Vite Cache Works

Performance and Disk Space Implications

Manual Cache Management

Your perspective belongs here.

0 question comments