Repository navigation
chore(size): batch re-record after #4529, #4533, #4494, #4534, #4532 - #4537
Conversation
Raises the compiled hydrating cap (32.56 -> 32.61 KB; minified fell 35 B, the brotli rise is mangle layout from #4494) and re-records minified on six rows that drifted toward the 20 B allowance. Floor caps are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
|
Size (brotli, eager entry chunk)
Bundled with Rolldown (what Vite ships), brotli q11, decimal KB. A scenario fails only when it is over its brotli cap and its minified size is more than 20 B over the minified recorded with the cap; over the cap within that allowance is brotli layout noise and passes with a warning. Caps and their recorded minified in |
Coverage Report for CI Build 41190406427Coverage remained the same at 78.134%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
Merging this PR will degrade performance by 0.18%2 warnings
Warning Please fix the performance issues or acknowledge them on CodSpeed. Performance Changes
Tip Investigate this regression by commenting Comparing Footnotes
|
Before: on next @ 3a73a36, "app: compiled hydrating" is 31 B over its brotli cap, and six rows sit 6–19 B over their recorded minified, close to the 20 B allowance. The next PR that touches them would fail the size gate on bytes it didn't add.
After: one ledger re-record for the batch. Only one cap rises, compiled hydrating, and its minified actually fell. The six drifted rows get their recorded minified updated. Floor caps are unchanged.
This follows the batch process: fix PRs don't edit
scripts/size, and the scan thread re-records once after a batch merges. The maintainer accepted the store-row growth from #4533 and #4534."hydrating + every store" doesn't need a re-record. #4494's rename puts it 43 B under its recorded minified even after #4529 and #4534. Hello world is 9,971 B, under its 9.98 KB cap, which is not raised.
How: the numbers are measured locally (linux) on next @ 3a73a36 with
scripts/size/size.mjs. If CI's head numbers differ, a follow-up commit will set the re-recorded rows to CI's values. Each row gets one dated ledger line.Size-Exception: re-records recorded minified on three frozen floors (hydrating no-stores, base server components, live server components). Their caps are unchanged. The growth comes from merged, accepted correctness fixes (#4529, #4533, #4532).
Generated by Claude Code