Bug/cache fingerprint assets#310
Merged
Mortaro merged 3 commits intonullstack:unstable-nextfrom Jan 26, 2023
Merged
Conversation
This file contains hidden or 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.
url.pathname.indexOf(self.context.environment.key) > -1to find fingerprinted assets, but it wasn't finding themstaleWhileRevalidatestrategy for requests to/client.js?fingerprint=0270f3e40e56449d6de75b1a73e4c1d0843e6ef0for example?=is not part of the pathname. I logged the pathname and it only returned/client.jsurl.searchParams?.get('fingerprint') === self.context.environment.keyto get the fingerprint param. This properly activates the cacheFirst strategyNullstack docs for fingerprinted assets strategy:
https://nullstack.app/service-worker#server-side-render-strategy
Url.pathname docs:
https://developer.mozilla.org/en-US/docs/Web/API/URL/pathname#examples