Add support for an optional faster file hashing method in Gatsby core #38891
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
This adds a new environment flag
GATSBY_FAST_HASHING
. If set, instead of cryptographically hashing files to check if they've changed, it will use a content digest comprised of the modification time and the inode. This is slightly less robust, but significantly faster especially on sites with lots of large files.This is the same as the optional feature added to
gatsby-source-filesystem
here: #37464Documentation
The flag has been added to
flags.ts
. Not sure if any other web documentation would need to be added, or if it should be flagged as experimental.Tests
No tests were added because this doesn't add new functionality, it just changes how existing functionality works, so existing tests should cover it.
Related Issues
Addresses #38887