You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(size): re-record the ledger after #4511 and for #4510 - #4521
Before: next @ 6bde511 has four rows over their brotli cap after #4511, though each is within the 20 B minified allowance. Those rows are hydrating no-stores (+43 B), base server components (+29 B), compiled live server components (+11 B) and observe + attribution (+4 B). #4510's size check is red on five rows.
After: the ledger records the post-#4511 sizes, plus #4510's growth, which the maintainer accepted on 2026-10-31. #4510 goes green once next is merged into it.
How: I measured next @ 6bde511 and #4510 with next merged in (bc3dfdf). For each row I took the larger of the two. Caps are measured brotli + 10 B, rounded up to 0.01 KB. Rows that are only past the minified allowance re-record minified and keep their caps. The local size.mjs gate passes on both builds with this ledger. The local #4510 numbers match its CI run on 5429aa0.
Hello world is unchanged and stays under its 9.98 KB cap.
Size-Exception: frozen floors hydrating (no stores), base server components and live server components are re-recorded for #4511 (merged 2026-10-30) and #4510; the maintainer accepted that growth on 2026-10-30 and 2026-10-31.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
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 scripts/size/scenarios.js; the floor and page caps in floor-caps.json are frozen (lower only, or Size-Exception: in the PR body). npm run ratchet lowers caps per RC; it never raises one (scripts/size/README.md).
System calls cannot be simulated consistently and are left out of the measure. The reported value understates the real cost. Switch to the Walltime instrument to measure them.
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
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.
Before: next @ 6bde511 has four rows over their brotli cap after #4511, though each is within the 20 B minified allowance. Those rows are hydrating no-stores (+43 B), base server components (+29 B), compiled live server components (+11 B) and observe + attribution (+4 B). #4510's size check is red on five rows.
After: the ledger records the post-#4511 sizes, plus #4510's growth, which the maintainer accepted on 2026-10-31. #4510 goes green once next is merged into it.
How: I measured next @ 6bde511 and #4510 with next merged in (bc3dfdf). For each row I took the larger of the two. Caps are measured brotli + 10 B, rounded up to 0.01 KB. Rows that are only past the minified allowance re-record minified and keep their caps. The local
size.mjsgate passes on both builds with this ledger. The local #4510 numbers match its CI run on 5429aa0.Hello world is unchanged and stays under its 9.98 KB cap.
Size-Exception: frozen floors hydrating (no stores), base server components and live server components are re-recorded for #4511 (merged 2026-10-30) and #4510; the maintainer accepted that growth on 2026-10-30 and 2026-10-31.
Generated by Claude Code