Skip to content

docs: update Next.js middleware description #6155

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.

Sign up for GitHub

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

Open
kostyniuk wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: update Next.js middleware description #6155

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/start/framework/react/comparison.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -242,7 +242,7 @@ const authMiddleware = createMiddleware({ type: 'function' })
})
```

**Next.js** has a single middleware.ts file that runs on the Edge Runtime for all requests. It cannot access server-only resources like databases and has limitations compared to Node.js runtime.
**Next.js** has a single proxy.ts file that runs on the Edge Runtime for all requests. It cannot access server-only resources like databases and has limitations compared to Node.js runtime.
Copy link
Contributor

@coderabbitai coderabbitai bot Dec 20, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Inaccuracy: proxy.ts runs on Node.js runtime, not Edge Runtime.

The proxy runtime is Node.js, and it cannot be configured; the edge runtime is NOT supported in proxy. The documentation currently claims proxy.ts "runs on the Edge Runtime," which contradicts the official Next.js 16 documentation. Please correct this to accurately reflect that proxy.ts runs on the Node.js runtime.

🔎 Proposed fix 
-**Next.js** has a single proxy.ts file that runs on the Edge Runtime for all requests. It cannot access server-only resources like databases and has limitations compared to Node.js runtime.
+**Next.js** has a single proxy.ts file that runs on the Node.js runtime. Unlike the deprecated middleware.ts (which ran on Edge Runtime), proxy.ts has full access to server-side resources like databases.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
**Next.js** has a single proxy.ts file that runs on the Edge Runtime for all requests. It cannot access server-only resources like databases and has limitations compared to Node.js runtime.
**Next.js** has a single proxy.ts file that runs on the Node.js runtime. Unlike the deprecated middleware.ts (which ran on Edge Runtime), proxy.ts has full access to server-side resources like databases.
🤖 Prompt for AI Agents 
docs/start/framework/react/comparison.md around line 245: the doc incorrectly
states that Next.js proxy.ts runs on the Edge Runtime; update the sentence to
state that proxy.ts runs on the Node.js runtime (cannot be configured to Edge)
and clarify that it therefore can access server-only resources like databases
while edge runtime is not supported for proxy.

Copy link
Contributor

@schiller-manuel schiller-manuel Dec 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kostyniuk what about this comment here? we also should probably mention both, next 15 and next 16

Copy link
Contributor

@coderabbitai coderabbitai bot Dec 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like the humans are having a chat. I'll hop back into my burrow for now. If you need me again, just tag @coderabbitai in a new comment, and I'll come hopping out!


### Deployment Flexibility

Expand Down