docs: Middleware fetching is not cached#80378
Merged
Conversation
ijjk
added
created-by: Next.js DevEx team
icyJoseph
commented
Jun 10, 2025
docs/01-app/03-building-your-application/01-routing/14-middleware.mdx
Outdated
Show resolved
Hide resolved
huozhi
approved these changes
Jun 10, 2025
ismaelrumzan
approved these changes
Jun 10, 2025
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
Closes: https://linear.app/vercel/issue/DOC-4751/docs-missing-middleware-caching-information-also-ts-types-issue
Fixes: #77900
Note that the TypeScript (should the TS plugin detect fetch
options.nextused in middleware and error out?) issue is still pending. It will be eventually handled.