Server side fetch during dev and production runs different
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Environment
nodejs
Reproduction
https://stackblitz.com/edit/github-yjfey7sb?file=server%2Froutes%2Findex.ts
Describe the bug
During development the the server side fetch can not resolve files in the public directory.
Once the app is build the server side fetch can resolve the public files and everything works as expected
Additional context
This was found in nuxt: https://github.com/nuxt/nuxt/issues/13857
Logs
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 and its server/routes/index.ts entry point, comparing the server-side fetch behavior during development and after a production build. Trace how public-directory files are resolved in each mode; done means the same fetch resolves those files in both development and production.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100