fix(anthropic): Fix streaming deadlock in Cloudflare Workers #10727
+21
−21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes a streaming deadlock issue when using
@ai-sdk/anthropicwithstreamText()in Cloudflare Workers.Problem
The
doStream()method uses atee()+ async first-chunk read pattern to trigger the transform stream:This causes a deadlock in Cloudflare Workers because:
doStream()returnsdoStream()returns a promise that waits for the transform to process a chunkThis works in Node.js but fails in CF Workers due to differences in how pull-based streams are handled.
Solution
Remove the
tee()pattern and resolve the promise immediately with the stream:Error handling for HTTP 200 responses with error payloads is still done in the transform function via the
isFirstChunkcheck.Test Plan
streamText()in Cloudflare WorkersRelated
This is a simpler alternative to #10726 that focuses only on the minimal fix needed.