vercel / vercel/examples

How to configure experimentalServices backend routePrefix

Open
#1,497 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
5.2k
Forks
1.8k
Avg merge
3d 12h
Merged PRs (30d)
6

Description

    "experimentalServices": {
        "frontend": {
            "entrypoint": "frontend",
            "routePrefix": "/"
        },
        "backend": {
            "entrypoint": "src/app.py",
            "routePrefix": "/api"
        }
    }
  • Backend FastAPI Routing: /api/auth/login
  • The request path in the logs is /auth/login; the /api prefix is ​​missing.
  • How do I configure the routePrefix for the backend?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the experimentalServices configuration shown in the issue and the backend entrypoint at src/app.py, then inspect how FastAPI routing and request paths are exposed. Document the supported routePrefix configuration and verify that a request to /api/auth/login has the expected path in the logs.

Written by the indexing model from the issue text.

Assessment

Tech stack
fastapi, python
Domain
api, backend
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.