`event.$fetch` returns HTTP 500, whereas `$fetch` works fine
Open
Nobody has claimed this yet.
bug
nuxt reproduction
v2
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Environment
n/a
Reproduction
https://stackblitz.com/edit/github-uhgm3j-qvnqae?file=server%2Fapi%2Ftest.post.ts
Describe the bug
Observe how calling the endpoint in server route with $fetch works correctly, and how it breaks with event.$fetch by returning HTTP 500.
Additional context
No response
Logs
No response
Contributor guide
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 with the StackBlitz reproduction in server/api/test.post.ts and compare the endpoint behavior when it calls $fetch versus event.$fetch. Run the reproduction and trace the failing event.$fetch path; done means the server route no longer returns HTTP 500 while the direct $fetch behavior remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100