support combining vercel edge with serverless
Open
Nobody has claimed this yet.
discussion
enhancement
v2
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Describe the feature
Like something in next.js, user can specify runtime for a route using a named export config.
I know there is a vercel-edge preset, but it is project wide.
export const config = {
runtime: 'edge',
}
export default (req) => new Response('Hello world!')
Additional information
- Would you be willing to help implement this feature?
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 by reading Nitro's vercel-edge preset and the route configuration handling referenced by the issue. Trace how the project-wide preset is applied, then determine how a named config export could select an edge runtime for one route while leaving other routes serverless. Done means both runtime modes work together with the behavior shown in the example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js, typescript
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100