ta
TanStack
GitHub
router
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
router
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
GitHub
router
Workspace
Succeeded
8392
835483a5 perf(start-client-core): load the server function RPC client lazily hydrateStart always registered ServerFunctionSerializationAdapter, whose static import of createClientRpc pulled serverFnFetcher, the frame decoder and seroval into every Start client bundle, including apps that define no server functions. The adapter now revives references through a small registry. The createClientRpc module registers itself, so apps whose compiled stubs already bundle it keep the exact same call path. Otherwise the RPC client is loaded on the first call of a revived reference. router-core's serializer modules also drop their value import of seroval's identity createPlugin helper so client hydration code carries no import edge to the seroval runtime.
by Sarah Gerrard
S
Failed
8392
Fix ready
→
835483a5 perf(start-client-core): load the server function RPC client lazily hydrateStart always registered ServerFunctionSerializationAdapter, whose static import of createClientRpc pulled serverFnFetcher, the frame decoder and seroval into every Start client bundle, including apps that define no server functions. The adapter now revives references through a small registry. The createClientRpc module registers itself, so apps whose compiled stubs already bundle it keep the exact same call path. Otherwise the RPC client is loaded on the first call of a revived reference. router-core's serializer modules also drop their value import of seroval's identity createPlugin helper so client hydration code carries no import edge to the seroval runtime.
by Sarah Gerrard
S
Previous
Next