refactor: utilize Vercel Build Output API to reimplement API proxy #822
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.
This replaces Vercel Edge Middleware with the Vercel Build Output API1 to reimplement the API proxy, cutting costs (no more invocation-based charges), reducing latency (no middle layer or cold starts), and simplifying the setup, while retaining dynamic configuration via the
VERCEL_PROXIED_API_BASE_URL
environment variable.Updates #804
Footnotes
https://vercel.com/docs/build-output-api/v3 ↩