Repository navigation
feat(router): add client routing and independent data fetchers - #64
Merged
Marcisbee merged 11 commits intoOct 22, 2026
Merged
Conversation
Marcisbee
marked this pull request as ready for review
October 22, 2026 16:10
Marcisbee
marked this pull request as draft
October 22, 2026 16:47
Marcisbee
marked this pull request as ready for review
October 22, 2026 17:41
Marcisbee
deleted the
kode/EJYFPDI1-add-client-routing-and-route-data-handli
branch
October 22, 2026 17:46
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.
Adds optional
radi/routerclient navigation, lazy route modules, loaders/actions, redirects, history, cancellation, and bounded opt-in prefetch caching. Independent data fetchers run loaders/actions without navigating or notifying route subscribers. Targeted invalidation retains unrelated cached routes, and fetcher disposal suppresses obsolete results.The Go/V8 example streams initial HTML and data, then uses Go JSON endpoints. Its reaction flow updates only the reaction component while preserving the draft and embedded document. Guides and API documentation explain local mutations, explicit refresh, redirects, cancellation, and cache boundaries.
CI cancels superseded runs, filters unrelated changes, limits job duration, and avoids duplicate master checks. Go tests use one race-enabled pass; extended soak checks run manually or on release. The Go browser check uses the runner’s installed Chrome, avoiding the Ubuntu dependency download that timed out. Documentation deployment and release publishing remain enabled.
Validation
All checks on commit 783fe0d passed: Go/server browser integration (1m19s), client/package checks (39s), documentation build (8s), and PR title (6s). Local validation also passed: 315 client tests, 11 router contracts, static/docs browser tests, Go race tests, npm build, and workflow lint (excluding its outdated Ubuntu 26.04 label inventory).
The Go browser test verifies SSR data reuse, prefetched navigation, history, mutation persistence, and three reaction add/remove cycles with no route reads or DOM mutations outside the reaction component. A fresh interaction video was captured from the running Go application.
Limits
Routes remain flat; nested loader hierarchies, full Remix compatibility, and automatic SSR hydration are not included. The example uses non-production in-memory data. Selective invalidation requires every affected URL/query variant; default mutation invalidation clears all cache entries. A broader strict check still reports existing Node/JSX declaration errors in unchanged renderer code. Direct master pushes now require manual checks before release.