nitropack upgrade introduces known regression: nuxt preview results in 404 response code on /:wildcard routes
Open
Nobody has claimed this yet.
nitro
upstream
- Dominant language
- TypeScript
- Stars
- 285
- Forks
- 33
- Avg merge
- 22h 38m
- Merged PRs (30d)
- 3
Description
Environment
unrelated
Reproduction
All info at https://github.com/nuxt/nuxt/issues/18932
This was introduced as a bug into nuxt bridge in https://github.com/nuxt/bridge/pull/695
There's a workaround but it's not well documented and digging in took 30 minutes
Describe the bug
Above
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 linked Nuxt issue #18932 and nuxt/bridge pull request #695, then reproduce the Nuxt preview request for /:wildcard routes. Trace the regression and document or correct the workaround so preview no longer returns a 404 for those routes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt, typescript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100