ta
TanStack
GitHub
router
Workspace
GitHub
CI Pipeline Executions
Current execution
Succeeded
fix/solid-router-route-scoped-accessor-teardown
Runs and Agents
Configuration
Self-Healing CI
Project Graph
Resource Usage
Analysis
Conformance
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
fix(solid-router): keep route-scoped accessors readable after navigation teardown Route-scoped accessors like Route.useParams() are backed by a lazy memo in useMatch. When async work created by a route component read the accessor after navigating away, the memo re-executed against the new matches and threw "Invariant failed: Could not find an active match". Track disposal of the owning reactive scope via onCleanup and return the last known value for reads that happen after teardown, while still throwing for mounted components that read a genuinely missing match. Fixes #7331 Closes #7330 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
nx run-many --target=build --exclude=examples/** --exclude=e2e/**
⌘K
Succeeded
nx run-many --target=build --exclude=examples/** --exclude=e2e/**
Click to copy
Linux
4 CPU cores
c206dc1e
7607
Get faster results
Learn how to enable distribution.
Atomizer enabled
43 groups of tasks optimized.