Repository navigation
feat(cache): expose configurable entry and byte budgets in v2 - #243
Merged
Merged
Conversation
jdalton
marked this pull request as ready for review
October 9, 2026 16:01
Owner
|
@davidwilder @jdalton you are making the difference ... awesome. |
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.
Summary
Expose numeric
CACHE_LIMITandCACHE_BYTESoptions throughconfigure()innwsapi2.x.Related to #242. This is a mitigation when a stylesheet fits the configured bounds. It does not resolve LRU thrashing for scans larger than those bounds. The V3 admission-policy change is intentionally outside this PR.
Validation
jsdom26.1.0 dependency, also 63 passed.git diff --checkpassed.No release or merge is included.