Update static export support details in documentation

[clicktodev]

Clarify the limitations of static export support in the comparison documentation, specifically noting that the App Router does not support useParams() on the client.

vercel/next.js#64660

Summary by CodeRabbit

• Documentation
  • Clarified framework comparison: static export support for Next.js now marked as partial, with a note about App Router limitations for client-side parameter access.

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

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the React framework comparison table to mark Next.js Static Export as partial (🟡) and add a note that the App Router does not support useParams() on the client; no other rows changed.

Changes

Cohort / File(s)	Summary
Documentation Update docs/start/framework/react/comparison.md	Modified Static Export row: changed Next.js indicator from ✅ to 🟡 (partial) and added note that App Router doesn't support useParams() on the client.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 I hopped through docs with careful paws,
Swapped a check for yellow, fixed the cause,
A client-side caveat softly penned,
Tiny change — clear guidance I send! ✨

🚥 Pre-merge checks | ✅ 3

✅ 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 directly and accurately reflects the main change: updating documentation about static export support details and limitations in Next.js.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

🤖 Fix all issues with AI agents

In @docs/start/framework/react/comparison.md:
- Line 69: Update the table row text to clarify the Static Export limitation:
replace the misleading "App Router doesn't support useParams()" with something
like "Static export requires generateStaticParams() for dynamic routes;
useParams() works client-side when routes are pre-generated", and ensure you
reference generateStaticParams and useParams by name in the copy; also, for the
🟡 partial support legend add a 1–5 rating value (e.g., "🟡 (2)") next to the
cell to follow the legend convention.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2e5e5c3 and 82e9813.

📒 Files selected for processing (1)

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

🧰 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

🧩 Analysis chain

🌐 Web query:

Next.js App Router static export useParams() limitation

💡 Result:

Short answer: With App Router and output: "export" (static HTML export), client-side useParams() can't get dynamic route values at build/runtime — App Router requires generateStaticParams() (or server params) to statically generate dynamic pages. If you use output: "export" without generateStaticParams for a dynamic segment, the build will error or the client hook can't be populated. [1][2][3]

What to do (brief):

• For static generation of dynamic routes, implement generateStaticParams() so pages are pre-built with params. [2]
• Or stop using output: "export" (use normal next build/deploy) so dynamic routes can be handled server-side/ISR.
• For client-only reads, parse window.location yourself as a fallback, but that's less ideal.

Sources:

• useParams() docs. [1]
• App Router static export limitations / static export guide. [2]
• GitHub issue/discussion showing the current limitation with output: "export" and useParams. [3]

---

🌐 Web query:

Next.js static export dynamic routes App Router client component hooks

💡 Result:

Short answer — yes, but with constraints.

Key points and steps

• Enable static export in next.config.js: output: 'export'. [1]
• For App Router dynamic routes you must provide all route params at build time via generateStaticParams (or avoid dynamic params). Dynamic routes without generateStaticParams (or with dynamicParams: true) are not supported for a static export. The app router renders Server Components at build to produce static HTML for each route produced by generateStaticParams. [1][2]
• Client components (use client) and React hooks (useRouter, useParams, useSearchParams, useEffect, etc.) run only in the browser. They are pre-rendered into the static HTML but any hook-driven runtime behavior runs on the client after hydration — they cannot produce new static routes at build time. Use client hooks for interactivity, but not for generating the list of static pages. [2]
• Unsupported features for static export include: dynamic routes without generateStaticParams, route handlers that depend on Request, cookies, rewrites/redirects/middleware, ISR, server actions, image optimization (default loader), etc. If you need those, you must deploy with a server (not output: 'export'). [1][2][3]

Practical recipe

1. In app/[slug]/page.tsx (server component) export async function generateStaticParams() { return [{ slug: 'a' }, { slug: 'b' }] } to enumerate pages. [1][2]
2. Keep page UI that needs browser-only APIs as a 'use client' child component and call hooks (useRouter/useParams/useEffect) there. Client hooks will work after hydration but cannot add build-time routes. [2]
3. Build: next build will emit static HTML files (out/). Deploy the out folder to any static host. [1]

Sources

• Next.js App Router — Static Exports guide. [1]
• Next.js docs: supported/unsupported features for static exports (client components, server components, generateStaticParams). [2]
• Warning/docs about API routes & static export limitations. [3]

---

🌐 Web query:

Next.js 15 App Router static export useParams() support compatibility

💡 Result:

Short answer: App Router + output: "export" (static HTML export) does not fully support client useParams() for dynamic routes unless you pre-generate those routes with generateStaticParams(); dynamic routes without generateStaticParams are listed as unsupported for static export. If you need dynamic client-side params without generateStaticParams, you must not use output: "export" (run with a server) or switch to an approach that pre-renders all param values. [1][2][3]

Sources:

• useParams API (App Router hooks). [1]
• GitHub discussion: "App Router with output: export does not support useParams() on client". [2]
• Next.js docs: Static Exports (unsupported features: dynamic routes without generateStaticParams). [3]

---

Clarify the Static Export limitation—it's about dynamic routes, not useParams() support.

The note "App Router doesn't support useParams()" is misleading. App Router supports the useParams() hook; the limitation is that static exports don't support dynamic routes unless routes are pre-generated via generateStaticParams(). With proper use of generateStaticParams(), client-side useParams() works fine.

Consider revising to: "Static export requires generateStaticParams() for dynamic routes" or similar, to accurately reflect the constraint.

Additionally, per the legend on line 23, partial support (🟡) should include a 1–5 rating where noted. Add one if applicable.

🤖 Prompt for AI Agents

In @docs/start/framework/react/comparison.md at line 69, Update the table row
text to clarify the Static Export limitation: replace the misleading "App Router
doesn't support useParams()" with something like "Static export requires
generateStaticParams() for dynamic routes; useParams() works client-side when
routes are pre-generated", and ensure you reference generateStaticParams and
useParams by name in the copy; also, for the 🟡 partial support legend add a 1–5
rating value (e.g., "🟡 (2)") next to the cell to follow the legend convention.