Update Middleware for Edge Environment Compatibility#55
Open
hisachin wants to merge 1 commit into
Open
Conversation
|
Someone is attempting to deploy a commit to the mickasmt's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Issue:
The Vercel build was failing due to incompatibility with the Edge environment in the current middleware implementation. The issue was identified when deploying the application, resulting in runtime errors specific to Edge functions.
Solution:
Updated the middleware code to ensure compatibility with Vercel's Edge environment. This includes modifying the API routes and request handling logic to align with Edge function requirements, ensuring seamless deployment and execution.
Changes Made