fix(gatsby-plugin-netlify): Do not cache static query data #26387
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
I recently ran into some strange issues on my site that boiled down to queries that came from
useStaticQuery
being immutably cached. The underlying data fetched by the static queries had changed after a redeploy, but when the page loaded in browsers with a warm cache, the relevant components showed the stale data after a brief flash of the new data from the HTML (before JS had loaded).Since static queries are given a deterministic query hash based on the query itself (not the query results) and written to
/static/d/{queryHash}.json
, the resulting file is cached indefinitely per the/static/*
caching header.This PR gives these files the same cache headers as the
page-data.json
files generated by Gatsby, since their purpose is similar.