René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Add configurable size limit for persistent build cache with LRU eviction","articleBody":"### Command\n\nbuild, serve\n\n### Description\n\nThe Angular CLI persistent disk cache (`.angular/cache`) grows without bounds. On large projects, a single checkout accumulates tens of gigabytes of cached build artifacts. In our case, a single checkout reached **29 GB**.\n\nThis was previously raised in #25116 and closed as not feasible with Webpack. Since Angular 17+, the build system uses esbuild, so the original constraint no longer applies.\n\n### Describe the solution you'd like\n\nAdd a configurable size cap (e.g., `cli.cache.maxSize`) with LRU eviction when the limit is reached. This is a common pattern in build tooling — Turborepo, Gradle, and most browsers' HTTP caches all implement bounded persistent caches.\n\nExample configuration:\n```json\n\"cli\": {\n  \"cache\": {\n    \"enabled\": true,\n    \"maxSize\": \"2GB\"\n  }\n}\n```\n\nWhen the cache exceeds `maxSize`, the oldest/least-recently-used entries are evicted.\n\n### Describe alternatives you've considered\n\n- Periodically running `ng cache clean` or manually deleting `.angular/cache` — works but is a manual maintenance burden, especially for developers unaware the cache is growing.","author":{"url":"https://github.com/aqeelat","@type":"Person","name":"aqeelat"},"datePublished":"2026-06-07T11:30:28.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/33320/angular-cli/issues/33320"}