· Updated
This benefits virtually all server-side WebStream use cases, including React Server Components and Next.js streaming workloads. The upstream path is: npm package → Node.js merge → Node.js release → Vercel fluid runtime update. Once merged into Node.js, the gain extends to self-hosted deployments too, not just Vercel infrastructure.
If your apps use Node.js streaming, this performance gain lands without any code changes on your end. Vercel users get it automatically via fluid runtime; self-hosted Node.js deployments benefit once the upstream PR merges. If streaming latency matters to your stack, it's worth tracking.
WebStreams are a nice, ergonomic standard for streaming data. And they're fast too... right? Turns out: not always. On servers, we found they're up to 10x slower than Node.js streams. So we Ralph Wiggum'd WebStreams for the server, powered by Node internals ↓ https://t.co/YwjsvJozNH
More like this
OpenAIFeb 23
CloudflareFeb 24
VercelApr 10