Skip to content

Initial approach to deleting stale cache - #13875

Closed
fforres wants to merge 5 commits into
webpack:mainfrom
fforres:fforres/delete_stale_cache
Closed

Initial approach to deleting stale cache#13875
fforres wants to merge 5 commits into
webpack:mainfrom
fforres:fforres/delete_stale_cache

Conversation

@fforres

@fforres fforres commented Jul 27, 2021

Copy link
Copy Markdown

This PR addresses some of the issues presented in #13291

This PR creates a new purgeStaleCache prop inside the cache options object and passing it down to decide if we should delete the stale caches or not.

It also adds cacheLocation to the file serialization context

What kind of change does this PR introduce?
It's a feature

Did you add tests for your changes?
Not yet

Does this PR introduce a breaking change?
Nope

What needs to be documented once your changes are merged?
A new prop on filesystem cache.

@webpack-bot

Copy link
Copy Markdown
Contributor

For maintainers only:

  • This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
  • This needs to be backported to webpack 4 (issue will be created when merged)

@fforres
fforres force-pushed the fforres/delete_stale_cache branch from 95d746f to cb16fb2 Compare July 27, 2021 06:55
@fforres
fforres force-pushed the fforres/delete_stale_cache branch from b7ccd42 to 1343f2b Compare July 27, 2021 15:43
@webpack-bot

Copy link
Copy Markdown
Contributor

@fforres The most important CI builds failed. This way your PR can't be merged.

Please take a look at the CI results from azure (2 errors / 0 warnings) and appveyor (success) and fix these issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants