Repository navigation
chore(size): re-record the ledger after the 2026-10-30 merges - #4462
Conversation
createStore and the compiled CSR app were over their caps on next after #4454 and #4457 landed together; raise both by the cap rule and re-record the minified of every non-frozen scenario that moved. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
|
Size (brotli, eager entry chunk)
|
Coverage Report for CI Build 41063860524Coverage remained the same at 78.1%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
Merging this PR will improve performance by 9.94%2 warnings
Performance Changes
Tip Curious why performance improved? Comment Comparing Footnotes
|
Before: on
next@ 563b6b0, two scenarios fail the size gate:signals: + createStoreis 14,951 B brotli against a 14.95 KB cap and 36 B minified over its record, andapp: compiled CSRis 26,312 B against 26.31 KB, also +36 B minified. #4454 and #4457 each passed against their own base, but together they cross both caps. Every PR opened againstnextwould fail these two scenarios.After: both caps are raised by the cap rule (measured + 10 B, rounded up to 0.01 KB): createStore 14.97 KB / 43,924, compiled CSR 26.33 KB / 80,035. The recorded minified of every other non-frozen scenario that moved is set to its measured value, with caps unchanged. The hydrating + stores scenario drops by 302 B.
How:
scripts/size/scenarios.jsonly, with a one-line ledger comment per scenario. No frozen floor is touched (floor-caps.jsonunchanged). Brotli growth over the two raised caps is +1 B and +2 B; the minified growth is #4454'sstagedScreencheck and #4457's same-error skip.Generated by Claude Code