-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
feat: configure edge function at route level #12323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 4494428 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@kylesloper since you've been using this, has this allowed you to split your routes into both serverless and edge? Currently, the adapter has the limitation of only accepting the I've tried uploading a build to Netlify and it only detects a single function although I have two routes, one configured with edge. I'm afraid we'd need to first solve the aforementioned issue and enable edge functions and split config to work with the adapter. |
Unlike the Vercel adapter, the Netlify Adapter currently doesn't support route level config or specifying an edge function at the route level. (e.g) all routes are normal lambda functions but a specific route is rendered on the edge using export config .
I've used this internally for a while but thought it may be helpful to the wider community.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.Edits