fix(gatsby): better heuristic for automatic cache purging #27682
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
A follow up for #27549. That PR didn't take into account that the
.cache
directory exists indevelop
by the moment we callinitialize
. In develop the.cache
directory is actually created here:gatsby/packages/gatsby/src/commands/develop.ts
Lines 99 to 102 in ed31b35
This PR uses a different heuristic to check for cache presence by just checking for
.cache/json
folder. We ensure this dir exists in the sameinitialize
method, so it seems an appropriate target for this check:gatsby/packages/gatsby/src/services/initialize.ts
Line 315 in ed31b35
Related Issues
Fixes #27641