taTanStackOSS
ta
  • Pipelines
  • Nx runs
Insights
  • Compare tasks
  • Analytics
rorouter
  1. Pipelines
  2. feat: context and control serialization of lifecycle methods `context`, `beforeLoad` and `loader` accept an object form `{ handler, dehydrate, hydrate }` (plus `revalidate` on `context` and `staleReloadMode` on `loader`) that controls what crosses the wire during SSR. Hydration restores what was sent and re-runs the rest; failures recover through the normal client load. The build strips `dehydrate` from the client and `hydrate`/`context.revalidate` from the server. The `context` option and `dehydrate`/`hydrate` are experimental. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
    nx affected --targets=test:eslint,test:unit,test:e2e,test:types,test:build,build --parallel=3
feat: context and control serialization of lifecycle methods
Failed after 8m 24sStarted
read access token used

nx affected --targets=test:eslint,test:unit,test:e2e,test:types,test:build,build --parallel=3

663128a28bfGitHubOpen on GitHub
TasksResource Usage
Resource usage is collected per agent
Run-level metrics are not available for distributed runs. Each agent’s CPU and memory are on the pipeline’s Resource Usage.

© 2026 Nx Cloud

  • Terms of Service
  • Privacy Policy
  • Changelog
  • Status
  • Docs
  • Contact Nx Cloud
  • Pricing
  • Company
  • @NxDevTools
taTanStackOSS