feat: fetchNodeHandler and toWebHandler #125
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
pi0
changed the title
fetchNodeHandlerfetchNodeHandler and nodeToFetchHandler
This was referenced Oct 18, 2025
pi0
changed the title
fetchNodeHandler and nodeToFetchHandlerfetchNodeHandler and toWebHandler
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR adds a built-in utility to convert Node handler format into Web.
This adds compatibility for fetching node handlers like Express.
When the handler is executed in a srvx node server, we detect it and use the fast path of directly passing the original node req, res through.
Otherwise, we create a virtual node Socket that streams input for the web Request body and intercepts raw writes to extract HTTP headers + streamed body.
This approach is fudumentally different than fetch-to-node and http-compute-js, and node-mock-http as those try to emulate all interfaces which in turns makes trouble for using with express (as express uses original node
OutgoingMessageprototype. See unjs/node-mock-http#5. This approach ensured Node.js behavior is untouched.Followup for Deno and Bun runtime support: #132