feat(site): preselect the largest load where ExoJS leads - #773
Merged
Merged
Conversation
Cards used to open on the load the harness marked primary, which carries no relation to how ExoJS actually did against its JavaScript peers there. openingSelection now opens each card on the largest load where ExoJS leads every JavaScript peer (Rapier excluded, since it is a Rust/WASM reference ceiling rather than a peer), or - failing that - the load it trails least, ties broken toward the larger load. The card states the reason inline when the choice was data-dependent. Every other load stays directly selectable; nothing changes about which loads or figures a card carries, only which one it opens on.
Exoridus
enabled auto-merge (squash)
September 22, 2026 16:03
Bundle ReportChanges will decrease total bundle size by 89 bytes (-0.0%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: site-server-esmAssets Changed:
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Cards used to open on the load the harness marked primary, which carries no relation to how ExoJS actually did against its JavaScript peers there.
openingSelectionnow opens each card on the largest load where ExoJS leads every JavaScript peer (Rapier excluded - it is a Rust/WASM reference ceiling rather than a peer, same split as the headline sentences), or - failing that - the load it trails least, ties broken toward the larger load. The card states the reason inline when the choice was data-dependent. Every other load stays directly selectable; nothing changes about which loads or figures a card carries, only which one it opens on.8 new unit tests for the selection function; existing bench site tests and typecheck stay green.