taTanStack
GitHubrouterWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceeded
      feat/solid-observe-navigation
    • Runs and Agents
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Circular DependenciesEnterprise
    • Resource Usage
    • Analysis
    • ConformanceEnterprise
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    feat(solid-router): declare navigations to Solid's observe tier On Solid's dev and observe builds the match publish inside startTransition is wrapped in OBSERVE.attribution.withOrigin: the ref names the destination route (fullPath, params, to/from pathnames) and dates from the history change that started the load, so the record spans the loader wait even though the publish comes after it. The pending offer, the initial load and same-location reloads are published undeclared. Production is unchanged (OBSERVE is undefined). Co-authored-by: Claude via Cursor <noreply@cursor.com> Co-authored-by: Cursor <cursoragent@cursor.com>
    nx run-many --target=build --exclude=examples/** --exclude=e2e/**
Succeeded
Linux
4 CPU cores
read access token used
bd74723a8399

Get faster results

Learn how to enable distribution.

Atomizer enabled

43 groups of tasks optimized.

Resource usage reports are turned off for this workspace

Your organization has the Resource usage add-on, but this workspace does not collect metrics for non distributed runs. Turn it back on in workspace settings.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools
GitHubrouterWorkspace