Skip to content

Commit dc35caf

Browse files
ryansolidClaude via Cursor
andcommitted
chore(size): the recovery record moves the observe tier 17.50 -> 17.55 KB
17,514 B against next's 17,487 (+27 B): the client hydration runtime's recover() and its registeredAt stamp, selected only under IS_OBSERVE. Prod scenarios byte-identical; engine -15 B of layout. Co-authored-by: Claude via Cursor <[email protected]>
1 parent 141be8c commit dc35caf

1 file changed

Lines changed: 11 additions & 1 deletion

File tree

‎scripts/size/.size-limit.js‎

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1917,7 +1917,17 @@ module.exports = [
19171917
// detach-before-run in the signals core landed over #3605 without a
19181918
// bump (its PR CI ran on the pre-#3605 base) and left this scenario 5 B
19191919
// over. Prod CSR is 15,819, byte-identical either way.
1920-
limit: "17.5 KB",
1920+
// Recovery record (#3623, 2026-09-23): 17.50 -> 17.55 KB, measured at
1921+
// 17,514 B against `next`'s 17,487 at c1b68d9d4 (+27 B). The client
1922+
// hydration runtime's `recover()` — the `s === 2` and `waitAndResume`
1923+
// rejection paths emit a `"recovery"` record ({ id, at, waitedMs,
1924+
// renderMs }) when `OBSERVE.records.observed("recovery")` — and its
1925+
// `registeredAt` stamp, both selected only under `IS_OBSERVE`. Prod
1926+
// hydrating (21,055), hydrating + stores (31,350) and CSR (15,854) are
1927+
// byte-identical to `next`; the engine scenario below moved -15 B of
1928+
// layout. (#3604 had already brought this scenario to 17,487 against
1929+
// the old 17.50 KB cap, 13 B under.)
1930+
limit: "17.55 KB",
19211931
modifyEsbuildConfig: observeEsbuildConfig
19221932
},
19231933
{

0 commit comments

Comments
 (0)