Repository navigation
feat: add lightweight server and client resumption - #60
Merged
Marcisbee merged 1 commit intoOct 22, 2026
Merged
Conversation
Marcisbee
marked this pull request as ready for review
October 22, 2026 10:54
Marcisbee
deleted the
kode/FrdCZgSN-add-lightweight-resumption-for-server-re
branch
October 22, 2026 11:05
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
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.
Server-rendered and streamed Radi pages can now handle clicks without recreating their DOM or rerunning component initialization.
resumablecarries escaped JSON state and a stream completion marker;resumeClicknames a trusted handler; the separateradi/resumebootstrap captures clicks and loads the requested handler on demand.Delivery is ordered per boundary, with independent boundaries, a bounded queue, loading timeout, retry after load failure, cancellation, and detached-target checks. The bootstrap must execute before interactive markup is parsed. This is an opt-in resumption API: existing closure-based components are not automatically hydrated, and navigation, form submission, and transient-user-activation APIs are not replayed. The documentation and runnable streaming example explain these boundaries.
Validation: 312 browser tests and 10 server tests pass. Type checks, npm build, and built-package export checks pass. Five Chromium HTTP-streaming runs captured two early clicks and keyboard activation while the handler response was delayed, then verified one delivery per interaction, one module request, and identity preservation for the original button and output text node. The example bootstrap is 3,929 minified bytes / 1,709 gzip bytes; warm click-to-text-mutation time was approximately 0.2 ms in each of five local runs. These local measurements exclude first-use network delay and are not field latency claims.
Implements Add lightweight resumption for server-rendered and streamed pages.