Overview - Router

router

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
6092
de2ef233 docs(page-level-hydration): soften runtime nav contract, flag future config Three call-outs to set the right expectation that today's SPA-stays-hydrated behavior on navigation into a hydrate:false route is the v1 default — a future router option will let you opt into hard-navigation/document-replace semantics, which is what enables Manuel's planned compile-time removal of hydrate:false route chunks from the main client bundle. Tweaks: - "When you set hydrate: false on a route" bullet list now scoped to initial page load; replaces a misleading "navigation = full page reload" bullet (which never matched runtime behavior) with a cross-ref to the navigation section. - "Client-side navigation into a hydrate:false route" section reads as a v1 default rather than a permanent contract; flags the upcoming option. - "When to use hydrate: false" bullets in both spots are scoped to initial load and note the upcoming optional follow-up for subsequent navigations.
by Tanner Lin...
Succeeded
6092
5e1d35c1 docs: rename "Selective Hydration" to "Page-Level Hydration" React 18 already uses "Selective Hydration" for its priority-based subtree hydration feature, which is a different mental model from what this PR ships (route-level on/off hydration). Rename the guide and nav entry to avoid the collision, and add a callout up top distinguishing the two. No code/API surface changes — the `hydrate` route option and `defaultHydrate` router option stay as-is. Just docs + the test describe label.
by Tanner Lin...
Succeeded
6092
adedc38f fix(selective-hydration): emit DEV hydrate-conflict warning from SSR + client Previously the conflict warning lived only in a client effect, so a `hydrate: false` route with a conflicting child silently skipped the warning during server rendering. Extract a `warnHydrateConflictOnce` helper (DEV-only, deduped per router instance via a WeakSet) and call it synchronously during render in all three adapters' Scripts so it fires on SSR too; keep the existing client effect to also catch conflicts introduced after navigation. Also align the warning text shown in the docs with the actual emitted message and add a `text` language hint to the fenced block (md040).
by Tanner Lin...
Failed
6092
Flaky task→
2f3632fe refactor: move client-entry strip helpers to start-client-core, expose scriptFilter hook - Add typed `scriptFilter` option on RouterOptions; adapter `<Scripts />` invokes it per script tag with `{ shouldHydrate }`. Adapters no longer import strip helpers. - Move `isClientEntryScript`, `stripClientEntryImport`, and a default `clientEntryScriptFilter` from router-core to @tanstack/start-client-core. Router-only consumers no longer ship the Start-specific strip helpers. - Auto-register `clientEntryScriptFilter` in Start's two router-options injection points: `hydrateStart` (client) and `createStartHandler.getRouter` (server). Zero authoring change for Start users. - Router-only SSR users can opt in via `createRouter({ scriptFilter: clientEntryScriptFilter })` or wire their own filter. - Add focused tests for the strip helpers under start-client-core; keep the react-router Scripts test verifying the filter mechanism with an inline filter.
by Tanner Lin...
Canceled
6092
2f3632fe refactor: move client-entry strip helpers to start-client-core, expose scriptFilter hook - Add typed `scriptFilter` option on RouterOptions; adapter `<Scripts />` invokes it per script tag with `{ shouldHydrate }`. Adapters no longer import strip helpers. - Move `isClientEntryScript`, `stripClientEntryImport`, and a default `clientEntryScriptFilter` from router-core to @tanstack/start-client-core. Router-only consumers no longer ship the Start-specific strip helpers. - Auto-register `clientEntryScriptFilter` in Start's two router-options injection points: `hydrateStart` (client) and `createStartHandler.getRouter` (server). Zero authoring change for Start users. - Router-only SSR users can opt in via `createRouter({ scriptFilter: clientEntryScriptFilter })` or wire their own filter. - Add focused tests for the strip helpers under start-client-core; keep the react-router Scripts test verifying the filter mechanism with an inline filter.
by Tanner Lin...
Succeeded
6092
3ae72e59 fix: ci failures for selective hydration - transformAssets test: include data-tsr-client-entry attr in expected client-entry script tag - vue hydrate-true e2e fixture: use defineComponent so reactive ref updates render
by Tanner Lin...
Failed
6092
Fix ready→
3ae72e59 fix: ci failures for selective hydration - transformAssets test: include data-tsr-client-entry attr in expected client-entry script tag - vue hydrate-true e2e fixture: use defineComponent so reactive ref updates render
by Tanner Lin...
Failed
6092
Fix ready→
1c091440 test(solid-start, vue-start): selective hydration e2e fixtures + solid docs - Mirror hydrate-true / hydrate-false fixtures and spec into solid-start and vue-start basic e2e - Add selective-hydration guide for the Solid Start docs and link it in the docs config - Fix the React guide's defaultHydrate example to use createRouter (not createStart)
by Tanner Lin...
Canceled
6092
1c091440 test(solid-start, vue-start): selective hydration e2e fixtures + solid docs - Mirror hydrate-true / hydrate-false fixtures and spec into solid-start and vue-start basic e2e - Add selective-hydration guide for the Solid Start docs and link it in the docs config - Fix the React guide's defaultHydrate example to use createRouter (not createStart)
by Tanner Lin...