-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Delete edge functions examples #1135
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Edge Functions are being deprecated in the future. We recommend using the full Node.js runtime with Fluid compute instead. Learn more here or read the docs. Functions using Fluid retain the benefits of Edge Functions, without the downsides of the limited Edge runtime. Further, most workloads have 1-3 regions for their data storage, where you should co-locate your compute. Ensure your Vercel Function region is the same as your database.
Places where these folders were linked (through Vercel templates) have been updated.
Edit: Since this PR has been shared, I should note this is me doing the pre-work before the work 😄 There will be much more on this in the coming months, including comms to existing customers. For more, this is me cleaning up how new accounts get started, which should be on Fluid. If you have Edge Functions today, you might consider moving to Fluid anyway, but you don't need to take any immediate action. Hold tight for official channel comms!