createCall's incoming request is not a readable stream
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 17
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Environment
NA
Reproduction
import { createCall } from "unenv/runtime/fetch/index";
createCall(async (req, res) => {
console.log(req.readable); // false
console.log(req.readableLength); // 0
console.log(req.header["content-length"]); //undefined
})({url: '/', body: 'test'})
Describe the bug
While the real node implementation of a server would have req.readable = true and readableLength = 4 as well as a content-length = 4 header
Additional context
No response
Logs
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at unenv/runtime/fetch/index, where the issue imports createCall, and run the provided reproduction with a request body of 'test'. Trace how the incoming request is constructed; done means its readable state, readableLength, and content-length header match the stated Node server behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100