-
Notifications
You must be signed in to change notification settings - Fork 29.7k
docs: use cache feedback #85169
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.
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
docs: use cache feedback #85169
Conversation
|
All broken links are now fixed, thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additional Comments:
docs/01-app/01-getting-started/06-partial-prerendering.mdx (line 9):
This file contains broken links to the deleted ppr.mdx documentation file. Since docs/01-app/03-api-reference/05-config/01-next-config-js/ppr.mdx has been deleted and its functionality consolidated under cacheComponents, these links need to be updated.
View Details
📝 Patch Details
diff --git a/docs/01-app/01-getting-started/06-partial-prerendering.mdx b/docs/01-app/01-getting-started/06-partial-prerendering.mdx
index 8d4b776330..113153d97d 100644
--- a/docs/01-app/01-getting-started/06-partial-prerendering.mdx
+++ b/docs/01-app/01-getting-started/06-partial-prerendering.mdx
@@ -6,7 +6,7 @@ related:
title: Next Steps
description: Learn more about the config option for Partial Prerendering.
links:
- - app/api-reference/config/next-config-js/ppr
+ - app/api-reference/config/next-config-js/cacheComponents
---
Partial Prerendering (PPR) is a rendering strategy that allows you to combine static and dynamic content in the same route. This improves the initial page performance while still supporting personalized, dynamic data.
@@ -109,7 +109,7 @@ To reduce network overhead, the full response—including static HTML and stream
## Enabling Partial Prerendering
-You can enable PPR by adding the [`ppr`](https://rc.nextjs.org/docs/app/api-reference/next-config-js/ppr) option to your `next.config.ts` file:
+You can enable PPR by adding the [`ppr`](/docs/app/api-reference/config/next-config-js/cacheComponents) option to your `next.config.ts` file:
```ts filename="next.config.ts" highlight={5} switcher
import type { NextConfig } from 'next'
Analysis
Broken documentation links to deleted ppr.mdx file
What fails: docs/01-app/01-getting-started/06-partial-prerendering.mdx contains two broken links pointing to the deleted docs/01-app/03-api-reference/05-config/01-next-config-js/ppr.mdx file.
How to reproduce:
- Check line 9 (frontmatter related links): references
app/api-reference/config/next-config-js/ppr - Check line 112 (inline link): references
https://rc.nextjs.org/docs/app/api-reference/next-config-js/ppr - Verify these files/URLs don't exist:
find docs -name "ppr.mdx" # Returns nothingResult: The documentation has broken links that will result in 404 errors when users try to access the PPR configuration documentation. The ppr.mdx file has been deleted (confirmed by glob search returning no results).
Expected: Links should point to valid documentation. According to cacheComponents.mdx version history (v16.0.0), the ppr configuration flag is now controlled by the unified cacheComponents configuration. The links have been updated to point to /docs/app/api-reference/config/next-config-js/cacheComponents which documents where PPR configuration is now located.
Fix: Updated both broken links to point to the cacheComponents documentation where PPR configuration is now unified with useCache and dynamicIO flags.
No description provided.