docs: update Next.js middleware description

[kostyniuk]

🎯 Changes

Update Next.js middleware description to match the Next.js 16 syntax.

✅ Checklist

• I have followed the steps in the Contributing guide.

🚀 Release Impact

• This change is docs/CI/dev-only (no release).

Summary by CodeRabbit

• Documentation
  • Updated middleware architecture reference in the React framework comparison guide.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A documentation file was updated to replace a reference from middleware.ts to proxy.ts in the "Middleware Architecture" section of the React framework comparison guide.

Changes

Cohort / File(s)	Summary
Documentation reference update docs/start/framework/react/comparison.md	Updated middleware architecture reference from middleware.ts to proxy.ts

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

documentation

Poem

🐰 A reference was shifted, from one name to the next,
The rabbit now hops through proxy.ts, context correct,
No logic was bent, just a pathway made clear,
Documentation's now tidy—the way we hold dear! 📚✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: updating a Next.js middleware reference in documentation from middleware.ts to proxy.ts to match Next.js 16 syntax.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 27d1c5e and 4745e4c.

📒 Files selected for processing (1)

• docs/start/framework/react/comparison.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

docs/**/*.{md,mdx}

📄 CodeRabbit inference engine (AGENTS.md)

Use relative links to docs/ folder format (e.g., ./guide/data-loading) for internal documentation references

Files:

• docs/start/framework/react/comparison.md

[coderabbitai]

⚠️ 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.

[schiller-manuel]

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

[coderabbitai]

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!