# feat(remix): scaffold remix-router, remix-start, and basic example Brings up an experimental TanStack Router binding to Remix 3 (`@remix-run/ui`) plus the Start adapter and a working basic example. ## What's in the box | Package | LOC (src) | Status | |---|---|---| | `@tanstack/remix-router` | 7,351 | Scaffold complete; binding works for the surface listed below | | `@tanstack/remix-start` | 479 | Server entry, default-entry server/client, vite plugin wrapper, `useServerFn` | | `examples/remix/basic` | 2,100 | Full-tree-hydrated demo; 16 working routes | | `examples/remix/islands` | 264 | Pure-Remix-3 reference using `@remix-run/ui` directly (no TanStack), demonstrates idiomatic island hydration | | Tests in `packages/remix-router/tests` | 3,917 | 28 test files | For comparison: `react-router` src is 6,699 LOC, `solid-router` is 5,487. `react-start` is 251, `solid-start` is 127. ## Build & test | Check | Result | |---|---| | `nx run @tanstack/remix-router:build` | ✅ pass | | `nx run @tanstack/remix-start:build` | ✅ pass | | `nx run @tanstack/remix-router:test:unit` | 111/120 pass (92.5%) | | `examples/remix/basic` `pnpm build` | ✅ pass — emits client + server bundles | | Type-check across binding | ✅ no errors | The 9 test failures are all in `tests/serverComponent.test.tsx` and `tests/dom/serverComponent.test.tsx`. They fail because `_resetServerComponentRegistry` and `deactivateServerComponentCollector` aren't exported from the source — the test scaffold was added before the implementation. Not blocking; tracked as a follow-up below. ## Bundle size (basic example, production build) | Slice | Raw | Gzip | |---|---|---| | Total client JS (all chunks) | 296 kB | 64 kB | | Initial entry (`index` + `useRouter`) | ~140 kB | ~46 kB | | Per-route lazy chunks | 0.5–7 kB each | 0.2–3 kB each | | Server bundle | 556 kB | — | Initial-load gzip (~46 kB) is dominated by the router runtime + Remix UI reconciler. The whole route tree hydrates as one Remix UI mount — there is no per-component selective hydration. This is intentional: TanStack Router's reactive store subscriptions need to be live across the route tree. For comparison, `examples/remix/islands` (no TanStack Router, pure `@remix-run/ui` islands via `run()`) demonstrates what selective hydration would look like: only `clientEntry()`-marked regions ship as hydration roots, and the rest is inert HTML. That's a different stack, not a different mode of this one. ## Routes that work in the basic example | Path | Demonstrates | Status | |---|---|---| | `/` | Static welcome page | ✅ | | `/users`, `/users/$id` | Loader-driven list, nested detail via `` | ✅ | | `/posts`, `/posts/$slug` | `createServerFn` rendering markdown HTML; mounted via `innerHTML` | ✅ | | `/admin/users/$userId/sessions/$sessionId` | 4-deep nested layout via file path | ✅ | | `/catalog?…` | `validateSearch`, `loaderDeps`, ``, form-driven `useNavigate` | ✅ | | `/slow` | Async loader, `pendingComponent` UI | ✅ | | `/lab/error` | Loader throws → `errorComponent` (intentional 500) | ✅ | | `/lab/missing` | `notFound()` → `notFoundComponent` (intentional 404) | ✅ | | `/lab/render-error` | Render-time throw caught by `` | ✅ | | `/guestbook` | `createServerFn({ method: 'POST' })` with `inputValidator`; form `on('submit')` calls server fn | ✅ | | `/counter` | `clientEntry()`-marked island embedded in route component | ✅ | ## What's not (yet) covered Three pieces are partially implemented and need follow-up work in the binding before the corresponding example routes can ship: ### 1. `` server-fn–backed boundaries - The example expected `renderPostBody.url(slug)` (curried). `.url` is a string property, not a function. Manuel Schiller's [`buildServerFnUrl` PR (branch `origin/buildServerFnUrl`)](https://github.com/TanStack/router/commit/28325f8628) lands a `buildServerFnUrl(fn, input): Promise` helper; once merged, the example loader can precompute the URL. - Independent of the URL helper, SSR still throws `No resolveFrame provided` from a recursive `renderToStream` call. The remix-router top-level handler does pass `resolveFrame`, but inner renders (when a frame's `src` is itself a route URL) don't get the option threaded through. Needs `resolveFrame` to be a property of the request context rather than an option of the outer `renderRouterToStream` call. ### 2. `` / `defer()` SSR streaming - ✅ **Landed in this PR**: `awaited.tsx` `onSettle → handle.update()` now skips on the server. The post-stream `scheduleUpdate not implemented` crash is gone. - ❌ **Still broken**: the seroval streaming chunks for the resolved deferred value are enqueued in `scriptBuffer.enqueue` but don't reach the response body. The server holds the connection open for the deferred duration, but the only `