Skip to content

docs: add generateStaticParams to Cache Components migration guide#92382

Open
aurorascharff wants to merge 1 commit intocanaryfrom
docs/migrating-cache-components-generate-static-params
Open

docs: add generateStaticParams to Cache Components migration guide#92382
aurorascharff wants to merge 1 commit intocanaryfrom
docs/migrating-cache-components-generate-static-params

Conversation

@aurorascharff
Copy link
Copy Markdown
Member

What?

Adds a generateStaticParams section to Migrating to Cache Components.

Why?

Developers migrating dynamic routes (for example blogs with [slug]) had no guidance in that guide for how generateStaticParams behaves with Cache Components, why next build can show ◐ instead of ○, or that return [] becomes a build error.

How?

  • Link to generateStaticParams with Cache Components, dynamic routes with Cache Components, and the empty-generate-static-params message doc instead of duplicating full behavior.
  • Before/after example: empty array vs at least one sample param.
  • Short note on ◐ (Partial Prerender) with links to the public pages PPR section and glossary.

Made with Cursor

…guide

- Document that generateStaticParams remains valid with links to API and dynamic-routes Cache Components docs
- Note empty-array migration and link to empty-generate-static-params message
- Add before/after example (return [] vs sample param)
- Explain ◐ vs ○ build output with links to public-pages PPR section and glossary

Made-with: Cursor
@nextjs-bot nextjs-bot added created-by: Next.js DevEx team PRs by the DX team. Documentation Related to Next.js' official documentation. labels Apr 5, 2026
@aurorascharff aurorascharff marked this pull request as ready for review April 5, 2026 12:23
Copilot AI review requested due to automatic review settings April 5, 2026 12:23
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds guidance for generateStaticParams behavior when migrating dynamic routes to Cache Components, including links to the canonical API docs and a brief explanation of why build output may show Partial Prerendering.

Changes:

  • Adds a new generateStaticParams section to the Cache Components migration guide.
  • Documents that return [] becomes a build error under Cache Components and links to the relevant message doc.
  • Provides before/after TS/JS examples and links to Partial Prerendering docs/glossary.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

created-by: Next.js DevEx team PRs by the DX team. Documentation Related to Next.js' official documentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants