Remove edge middleware for routing Markdown requests#5
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
petradonka
approved these changes
Apr 30, 2026
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.
Summary
We're noticing that pageviews are unexpectedly missing in our dashboard. It's possible that edge middleware is swallowing these events.
The intent of this edge middleware is to route LLM requests to the Markdown format for pages when they present the text/markdown heading. In my testing, this doesn't work as expected, so it's worth removing this for now anyways until we can verify a working solution.
Follow-ups
We'll want to get a working version of LLM routing to Markdown routes working later.