feat: use Vercel KV for page content cache #100
Merged
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.
Goal
?fcr=1
to forcibly refresh cacheKnowledge Transfer / Notes
Only serverless and edge functions support
Cache-control
override. Page route doesn't support this, so we must maintain this cache logic ourselves.It's better to upgrade to Next.js v13 and React v18 to use the Data Cache in the future. However, I encounter some issues that cannot easily migrate it. Will revisit it later.
https://vercel.com/docs/infrastructure/data-cache