swagger-api / swagger-api/swagger-ui
Facing issue on deployed express ts api on vercel, works fine on local
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
shows No operations defined in spec! on vercel while on local i'm able to see specs and works fine with all routes.
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
Compare the OpenAPI output from the deployed Express TypeScript API on Vercel with the working local output, focusing on why the deployed Swagger UI reports “No operations defined in spec!”. Done means the deployed API exposes the same operations and routes as the local version.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100