In server side, the timeout setting is invalid, and the request cannot be aborted after the timeout.
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 195
- PR merge metrics
- No merged PRs in 30d
Description
Environment
node v22.14.0
Nuxt 3.16.0
ofetch 1.4.1
Reproduction
none
Describe the bug
In server side, the timeout setting is invalid, and the request cannot be aborted after the timeout.
In client side, it works well.
Additional context
No response
Logs
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 by reproducing the server-side timeout behavior in the listed Node v22.14.0 and Nuxt 3.16.0 environment, then compare it with the working client-side behavior. The issue has no reproduction, file, or test named; it is done when a server-side request is aborted after the configured timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, nuxt, typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100