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
Commit 6c5ab82
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: scripts/size/scenarios.js
+9-6Lines changed: 9 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -1419,9 +1419,10 @@ module.exports = [
1419
1419
// An isPending() probe wakes a dormant memo outside its window (#4366, 2026-10-28, over next @ 5f60713a): cap 10.38 KB unchanged, recorded minified 28,817 -> 28,680 B (+4 B minified over next), measured locally (linux) at 10,380 B brotli. A lazy or dormant memo (an unowned memo left with no reader) woken by a read inside `isPending`/`latest` recomputed inside the probe's window, so it derived from its sources' committed values; the wake now runs outside it, as a pull does (A31). Correctness. Recorded minified = measured; CI re-bases.
1420
1420
// A frame node re-run outside its hold re-derives the readers of the staging it replaces (#4378, 2026-10-28, over next @ b68942ca): cap unchanged, recorded minified 28,680 -> 28,693 B, measured locally (linux) at 10,384 B brotli / 28,693 B minified (+15 B minified over next). A held boundary output, and the boundary trees and outputs above it, re-run outside the hold published the committed fallback back unchanged, so their readers kept the hold's stale run of the content and the landing applied it: an empty hole. The re-derive sits in recompute's mainline-publish arm, the one place every frame node drops a staging. Correctness.
1421
1421
// Batch re-record (2026-10-29, over next @ 3b7ea81c): 10.38 -> 11.03 KB, recorded minified 29,086 -> 30,373 B (+1287 B), measured in CI at 11,019 B brotli. Growth is the 2026-10-29 bug-fix batch (#4401, #4397, #4383, #4393, #4406); the maintainer asked for one re-record on next after it (2026-10-29). Cap at measured + 10 B rounded up to 0.01 KB, never lowered; recorded minified = measured.
1422
-
limit: "11.03 KB",
1422
+
// Verdict and lane upkeep folds out of builds without those engines (2026-10-29, over next @ 9545058d): 11.03 -> 11.05 KB, recorded minified 30,373 -> 30,407 B (+34 B), measured in CI at 11,036 B brotli. The engines' hook guards: the floors drop 285 B minified (hello world 10,059 -> 9,967 B brotli, back under the 10 KB stop), a build with the verdict engine carries the guards. Cap at measured + 10 B rounded up to 0.01 KB; recorded minified = measured.
1423
+
limit: "11.05 KB",
1423
1424
// latest() read inline and through a memo show the same screen (#4284 through a memo; a plain write beside an async memo), 2026-10-29, over next @ 7ebd4a32: recorded minified 28,693 -> 29,086 B (+343 B minified over next), measured locally (linux) at 10,565 B brotli (+135 B over next). A render effect a verdict memo's change re-runs reads as its verdict reader for that pass (`laneDirty`), a pass that read a staging before the frame had a transaction re-derives once as a verdict reader only if the frame parks, `latest()` of a first load in flight in a verdict lane is loading (also through an identity memo, a derived store and `isPending`), a lane's dissolution leaves such a load and the nodes pending on it uninitialized instead of committing `undefined`, a verdict lane born at a seam is judged at it, a pass born in a staged reader stays the frame's on a verdict-memo read (C4, #4010), a plain write beside `latest()` computes once (the seam re-derives a pre-transaction staged reader only if the frame parks), a verdict reader's plain read of a staging in a transaction only a `latest()` opened is the frame's read, so a memo of `latest()` computes once too (D-22; not a pass with no value yet, D-6), and an error stays the display while the memo it came through re-asks, a Loading fallback behind it included (D-39, async-gen 91501 #1831). recompute's CONFIG_VERDICT clear now sits behind the lane engine: -21 B minified on every floor. Correctness; the maintainer: "only flag me if brotli goes more than 20kb" (2026-10-29). Cap unchanged; recorded minified = measured.
1424
-
capMinified: 30373,
1425
+
capMinified: 30407,
1425
1426
alias
1426
1427
},
1427
1428
{
@@ -5796,11 +5797,12 @@ module.exports = [
5796
5797
// A frame node re-run outside its hold re-derives the readers of the staging it replaces (#4378, #4390, 2026-10-28, re-recorded over next @ cbc0eebd): recorded minified 123,191 -> 123,203 B (+12 B minified over next's record), measured locally (linux) at 41,872 B brotli. Recorded minified = measured; CI re-bases.
5797
5798
// An Errored heals when the last reader that caught its error is disposed (#4373, 2026-10-28, re-recorded over next @ b68942ca): cap 41.56 KB unchanged, recorded minified 123,182 -> 123,228 B (+46 B minified over next's record), measured locally (linux) at 41,856 B brotli. A boundary's readers become a reader -> source map, so an error boundary waits on what threw only while a reader that caught it is alive. Correctness (Ryan's ruling on #4373). Recorded minified = measured; CI re-bases.
5798
5799
// Batch re-record (2026-10-29, over next @ 3b7ea81c): 41.56 -> 42.61 KB, recorded minified 123,733 -> 125,129 B (+1396 B), measured in CI at 42,595 B brotli. Growth is the 2026-10-29 bug-fix batch (#4401, #4397, #4383, #4393, #4406); the maintainer asked for one re-record on next after it (2026-10-29). Cap at measured + 10 B rounded up to 0.01 KB, never lowered; recorded minified = measured.
5799
-
limit: "42.61 KB",
5800
+
// Verdict and lane upkeep folds out of builds without those engines (2026-10-29, over next @ 9545058d): 42.61 -> 42.62 KB, recorded minified 125,129 -> 125,165 B (+36 B), measured in CI at 42,610 B brotli. The engines' hook guards: the floors drop 285 B minified (hello world 10,059 -> 9,967 B brotli, back under the 10 KB stop), a build with the verdict engine carries the guards. Cap at measured + 10 B rounded up to 0.01 KB; recorded minified = measured.
5801
+
limit: "42.62 KB",
5800
5802
// An Errored heals when the last reader that caught its error is disposed (#4373, #4384, 2026-10-28, re-recorded over next @ cbc0eebd): recorded minified 123,191 -> 123,249 B (+58 B minified over next's record), measured locally (linux) at 41,899 B brotli. Recorded minified = measured; CI re-bases.
5801
5803
// Boundary readers keyed by the source they wait on (#4373), with enterLane's tail folded into one else-chain as an offset (-29 B on lane pages) (#4384, 2026-10-28, re-recorded over next @ 1b32ff2e): recorded minified 123,203 -> 123,224 B (+21 B minified over next's record), measured locally (linux) at 41,966 B brotli. Recorded minified = measured; CI re-bases.
5802
5804
// latest() read inline and through a memo show the same screen (#4284 through a memo; a plain write beside an async memo), 2026-10-29, over next @ 7ebd4a32: recorded minified 123,224 -> 123,733 B (+403 B minified over next), measured locally (linux) at 42,119 B brotli (+169 B over next). A render effect a verdict memo's change re-runs reads as its verdict reader for that pass (`laneDirty`), a pass that read a staging before the frame had a transaction re-derives once as a verdict reader only if the frame parks, `latest()` of a first load in flight in a verdict lane is loading (also through an identity memo, a derived store and `isPending`), a lane's dissolution leaves such a load and the nodes pending on it uninitialized instead of committing `undefined`, a verdict lane born at a seam is judged at it, a pass born in a staged reader stays the frame's on a verdict-memo read (C4, #4010), a plain write beside `latest()` computes once (the seam re-derives a pre-transaction staged reader only if the frame parks), a verdict reader's plain read of a staging in a transaction only a `latest()` opened is the frame's read, so a memo of `latest()` computes once too (D-22; not a pass with no value yet, D-6), and an error stays the display while the memo it came through re-asks, a Loading fallback behind it included (D-39, async-gen 91501 #1831). recompute's CONFIG_VERDICT clear now sits behind the lane engine: -21 B minified on every floor. Correctness; the maintainer: "only flag me if brotli goes more than 20kb" (2026-10-29). Cap unchanged; recorded minified = measured.
5803
-
capMinified: 125129,
5805
+
capMinified: 125165,
5804
5806
alias: pageAlias
5805
5807
},
5806
5808
{
@@ -6188,11 +6190,12 @@ module.exports = [
6188
6190
// A frame node re-run outside its hold re-derives the readers of the staging it replaces (#4378, #4390, 2026-10-28, re-recorded over next @ cbc0eebd): recorded minified 140,451 -> 140,463 B (+12 B minified over next's record), measured locally (linux) at 47,529 B brotli. Recorded minified = measured; CI re-bases.
6189
6191
// An Errored heals when the last reader that caught its error is disposed (#4373, 2026-10-28, re-recorded over next @ b68942ca): cap 47.16 KB unchanged, recorded minified 140,442 -> 140,485 B (+43 B minified over next's record), measured locally (linux) at 47,463 B brotli. A boundary's readers become a reader -> source map, so an error boundary waits on what threw only while a reader that caught it is alive. Correctness (Ryan's ruling on #4373). Recorded minified = measured; CI re-bases.
6190
6192
// Batch re-record (2026-10-29, over next @ 3b7ea81c): 47.16 -> 48.29 KB, recorded minified 140,983 -> 142,390 B (+1407 B), measured in CI at 48,273 B brotli. Growth is the 2026-10-29 bug-fix batch (#4401, #4397, #4383, #4393, #4406); the maintainer asked for one re-record on next after it (2026-10-29). Cap at measured + 10 B rounded up to 0.01 KB, never lowered; recorded minified = measured.
6191
-
limit: "48.29 KB",
6193
+
// Verdict and lane upkeep folds out of builds without those engines (2026-10-29, over next @ 9545058d): 48.29 -> 48.31 KB, recorded minified 142,390 -> 142,427 B (+37 B), measured in CI at 48,298 B brotli. The engines' hook guards: the floors drop 285 B minified (hello world 10,059 -> 9,967 B brotli, back under the 10 KB stop), a build with the verdict engine carries the guards. Cap at measured + 10 B rounded up to 0.01 KB; recorded minified = measured.
6194
+
limit: "48.31 KB",
6192
6195
// An Errored heals when the last reader that caught its error is disposed (#4373, #4384, 2026-10-28, re-recorded over next @ cbc0eebd): recorded minified 140,451 -> 140,509 B (+58 B minified over next's record), measured locally (linux) at 47,516 B brotli. Recorded minified = measured; CI re-bases.
6193
6196
// Boundary readers keyed by the source they wait on (#4373), with enterLane's tail folded into one else-chain as an offset (-29 B on lane pages) (#4384, 2026-10-28, re-recorded over next @ 1b32ff2e): recorded minified 140,463 -> 140,485 B (+22 B minified over next's record), measured locally (linux) at 47,547 B brotli. Recorded minified = measured; CI re-bases.
6194
6197
// latest() read inline and through a memo show the same screen (#4284 through a memo; a plain write beside an async memo), 2026-10-29, over next @ 7ebd4a32: recorded minified 140,485 -> 140,983 B (+405 B minified over next), measured locally (linux) at 47,722 B brotli (+162 B over next). A render effect a verdict memo's change re-runs reads as its verdict reader for that pass (`laneDirty`), a pass that read a staging before the frame had a transaction re-derives once as a verdict reader only if the frame parks, `latest()` of a first load in flight in a verdict lane is loading (also through an identity memo, a derived store and `isPending`), a lane's dissolution leaves such a load and the nodes pending on it uninitialized instead of committing `undefined`, a verdict lane born at a seam is judged at it, a pass born in a staged reader stays the frame's on a verdict-memo read (C4, #4010), a plain write beside `latest()` computes once (the seam re-derives a pre-transaction staged reader only if the frame parks), a verdict reader's plain read of a staging in a transaction only a `latest()` opened is the frame's read, so a memo of `latest()` computes once too (D-22; not a pass with no value yet, D-6), and an error stays the display while the memo it came through re-asks, a Loading fallback behind it included (D-39, async-gen 91501 #1831). recompute's CONFIG_VERDICT clear now sits behind the lane engine: -21 B minified on every floor. Correctness; the maintainer: "only flag me if brotli goes more than 20kb" (2026-10-29). Cap unchanged; recorded minified = measured.
0 commit comments