babel / babel/babel-loader

Prune babel-loader's cache so it does not grow forever

Open
#634 2 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
JavaScript
Stars
4.8k
Forks
456
Avg merge
9h 19m
Merged PRs (30d)
2

Description

**I'm submitting a feature request**
Would it be possible to add a way to prune the babel-loader cache after webpack runs? We've started uploading/downloading our cache in CI to help performance across builds, but the babel-cache grows unbounded and eventually bogs down our CI.

**Babel Loader Version**:
7.1.4

**Current behavior:**
babel cache grows unbounded

**Expected/desired behavior:**
It doesn't.

Contributor guide

Open the contributing guide

Research direction

No file or test is named. Start by locating babel-loader's cache handling and the webpack lifecycle point relevant to pruning after a run; define how pruning should work without harming cache reuse, then verify through CI-style builds that the cache no longer grows without bound.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, webpack
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.