React Daily: Flight Server Backpressure Fix and CI Updates
React developers fixed a critical Flight Server streaming issue that caused data corruption under Node.js backpressure conditions. The team also enabled CI on backport branches for React 19.1.x and 19.2.x releases.
Duration: PT1M45S
Transcript
Good morning, this is React Daily for May 28th, 2026.
The React team merged four pull requests yesterday, headlined by a significant Flight Server fix. Hendrik Liebau merged a solution for stranded row content under Node stream backpressure. The issue occurred when Flight Server emitted text and typed array data as separate header and content chunks - if backpressure hit between these chunks, content could become stranded in the queue, leading to deserialization failures. The fix introduces an atomic sentinel system that ensures header-content pairs are written together, preventing data corruption while maintaining backpressure benefits.
Sebastian Silbermann merged three CI-related pull requests, enabling continuous integration on React's backport branches. The main change allows CI to run on release branches rather than tags, unifying the workflow with existing protected environment rules. Two additional PRs backported these CI fixes to the 19.1.x and 19.2.x branches, along with various dependency and configuration updates.
The Flight Server fix addresses a Node.js-specific issue that didn't affect browser environments, where the fake writable stream always returns true from write operations. The atomic chunk system uses sentinels to group related data without the memory overhead of concatenating large typed arrays.
What's next: Watch for these fixes to roll out in upcoming React releases, particularly affecting server-side rendering workflows. The improved CI setup should accelerate backport testing and release cycles.
That's your React Daily briefing. Stay updated at reactdaily.dev.