docs: add generateStaticParams to Cache Components migration guide#92382
Draft
aurorascharff wants to merge 2 commits intocanaryfrom
Draft
docs: add generateStaticParams to Cache Components migration guide#92382aurorascharff wants to merge 2 commits intocanaryfrom
aurorascharff wants to merge 2 commits intocanaryfrom
Conversation
…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
added
created-by: Next.js DevEx team
Contributor
There was a problem hiding this comment.
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
generateStaticParamssection 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.
aurorascharff
commented
Apr 7, 2026
aurorascharff
commented
Apr 7, 2026
Contributor
|
Hi there 👋 It looks like this PR introduces broken links to the docs, please take a moment to fix them before merging:
Thank you 🙏 |
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
| } | ||
| ``` | ||
|
|
||
| > **Good to know:** With Cache Components, each listed param shows its own symbol in the [build output](/docs/app/guides/building) — `○` if the page is fully static, or `◐` if it contains streamed content. See [Partial prerendering](/docs/app/guides/public-static-pages#partial-prerendering) for more details. |
Contributor
There was a problem hiding this comment.
Suggested change
| > **Good to know:** With Cache Components, each listed param shows its own symbol in the [build output](/docs/app/guides/building) — `○` if the page is fully static, or `◐` if it contains streamed content. See [Partial prerendering](/docs/app/guides/public-static-pages#partial-prerendering) for more details. | |
| > **Good to know:** With Cache Components, each listed param shows its own symbol in the [build output](/docs/app/api-reference/cli/next#next-build-options) — `○` if the page is fully static, or `◐` if it contains streamed content. See [Partial prerendering](/docs/app/guides/public-static-pages#partial-prerendering) for more details. |
Broken documentation link /docs/app/guides/building points to a non-existent page.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What?
Adds a
generateStaticParamssection to Migrating to Cache Components.Why?
Developers migrating dynamic routes (for example blogs with
[slug]) had no guidance in that guide for howgenerateStaticParamsbehaves with Cache Components, whynext buildcan show ◐ instead of ○, or thatreturn []becomes a build error.How?
generateStaticParamswith Cache Components, dynamic routes with Cache Components, and theempty-generate-static-paramsmessage doc instead of duplicating full behavior.Related: #92507