[cloudflare] add more information around what NEXT_CACHE_REVALIDATION_WORKER is
#97
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
james-elicx
approved these changes
Mar 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This change adds more context around what
NEXT_CACHE_REVALIDATION_WORKERis. This confused me originally when I was going through the docs to set up caching. Still not 100% sure if this is accurate, but I noticed in all of the e2e examples this binding was a self reference (and I don't see anywhere in the docs or in another project on Github describing creating this worker). Mostly just wanted to open this for discussion because I'm not sure where the best place is and thought I might be able to improve the docs for the next person who sees this.