taTanStack
GitHubrouterWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceededfeat/selective-hydration
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Resource Usage
    • Analysis
    • Conformance
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    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.
    nx run-many --target=build --exclude=examples/** --exclude=e2e/**
Succeeded
Linux
4 CPU cores
e85bb4a86092

Get faster results

Learn how to enable distribution.

Atomizer enabled

43 groups of tasks optimized.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools