Skip to content

Missed a link in README.md#7

Merged
zpao merged 1 commit intofacebook:masterfrom
jeffreylin:master
May 29, 2013
Merged

Missed a link in README.md#7
zpao merged 1 commit intofacebook:masterfrom
jeffreylin:master

Conversation

@jeffreylin
Copy link
Contributor

Whenever you have a spare moment =]

@carveR1209
Copy link

Whenever you have a spare moment

unstubbable pushed a commit to unstubbable/react that referenced this pull request Jan 23, 2026
switz added a commit to switz/react that referenced this pull request Mar 25, 2026
…cebook#7)

* TIM-472: Flight wire format and client boundary detection analysis

Comprehensive analysis covering:
- isClientReference() detection via Symbol.for('react.client.reference')
- ClientReference shape (99689typeof, 99689id, 99689async)
- Flight wire format: row format, chunk types (Model, Import, Error, etc.)
- Import chunk metadata: module ID, chunks array, export name
- Props serialization at client boundaries
- Async server component handling (thenable → ping → retry)
- Module reference resolution (build-time proxies → manifest → metadata)
- Implications for fused renderer: detection, extraction, manifest access

* TIM-482: go/no-go checkpoint — GO with narrow scope (Approach B+)

Decision: proceed with fused renderer using Approach B+ (Flight as library
+ focused props serializer), phased rollout starting with sync server
component execution in Fizz.

Key evidence:
- Flight overhead is 54-79% of total SSR time (TIM-483)
- Detection functions are trivially extractable (TIM-481)
- Hydration markers are backwards-compatible (TIM-473)
- Projected 2x throughput improvement

Phased approach:
- Phase 1: TIM-474, TIM-475 (server-side fusion)
- Phase 2: TIM-476, TIM-477 (client hydration optimization)
- Phase 3: TIM-478-480 (coexistence, benchmarks, edge cases)

Each phase is a decision gate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants