Skip to content

Add explicit document refresh API and React hook - #14

Closed
skmayya1 wants to merge 1 commit into
mainfrom
fix/explicit-document-refresh
Closed

skmayya1 wants to merge 1 commit into
mainfrom
fix/explicit-document-refresh

Conversation

@skmayya1

@skmayya1 skmayya1 commented Oct 15, 2026 •

Copy link
Copy Markdown

Same-route replacement does not request a fresh document. This leaves hosts with stale server state after a conflict response.

Add runtime.refresh() and useTurboLiteRefresh(). Explicit refresh and Stream refresh now share the same request path, preserve the document prefix and query, and leave native history unchanged. Prepare version 0.3.1 for the app adoption.

Validation: all 117 tests pass, including new Expo prefix/history and refresh failure/race tests. bun run check passes. Coverage passes at 91.46% lines and 84.35% branches.

Release blocker: bun run audit:ci fails on existing development dependencies (41 findings). The runtime dependency is unchanged. No registry release was attempted. Native device E2E has not run.

Packed-package validation: an isolated React/Expo adapter test imported the built tarball through its public exports. A stale transition returned 409; the refresh fetched the prefixed document with repeated query parameters; the retry used the new state version and succeeded. The runtime instance stayed the same, with no router push/replace. Successful document replacement can reset local controls.

The NoScrubs app uses this exact tarball while the registry release is blocked. Its shared and customer app type checks and cart registry tests pass.

@skmayya1 skmayya1 closed this Oct 15, 2026
@skmayya1
skmayya1 deleted the fix/explicit-document-refresh branch October 15, 2026 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant