Repository navigation
Version Packages - #33
Merged
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@leejpsd/nextjs-cache-handler@1.1.0
Minor Changes
247f38fThanks @leejpsd! - NewtagReadModeoption for the'use cache'handler (Consider reducing the amount of time spent on scan operations #31). The default,"scan", is unchanged:refreshTags()SCANs the namespace's tag markers into a local mirror on every request. Redis SCAN walks the whole keyspace regardless of the MATCH pattern, so that cost grows with the total number of keys in the database, not with the number of tags: about 20 ms per request at 20k keys and 65–170 ms at 100k against a local Redis.tagReadMode: "on-demand"turns the scan off;get()andgetExpiration()insteadMGETthe markers for exactly the tags they are given (the entry's own tags plus the route's soft tags), one extra round trip perget(), which is how the singular handler andgetExpiration()already worked.tagPubSubworks in either mode. Thanks @royvou for the report and the proposal.