fix: apply caching headers to all produced assets #217
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Port of gatsbyjs/gatsby#35494
This adds missing permament caching headers on some assets that are emitted by webpack. In particular this adds those headers to chunk files that were code split due to dynamic imports (
import('something')) - those are not handled with current implementation and result in default (?)cache-control: public, max-age=0, must-revalidate.You can compare results (visit, refresh, check network tab in DevTools) :
latest: https://63e388514621dd00b6e20e73--jade-bavarois-301e6e.netlify.app/dynamic/with changes from this pr: https://63e3c8f45bb3b000084802c9--jade-bavarois-301e6e.netlify.app/dynamic/
(left = latest, right = this pr)
Not every site will see benefits, but users of
@loadable/componentetc will by saving on unnecessary round trips to server (304s) if resource is already cached by the browser