Remove unnecessary Partial Prerendering (PPR) configuration

- Remove cacheComponents: true from next.config.mjs
- Update README.md to remove PPR references
- All pages are fully static-generated, PPR provides no benefit

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
2026-02-13 14:57:08 +08:00
parent 5a80567117
commit ed63ec7d9a
2 changed files with 1 additions and 4 deletions

View File

@@ -21,7 +21,6 @@ This blog is optimized for performance using Next.js 16 features and best practi
### Next.js 16 Features ### Next.js 16 Features
- **Partial Prerendering (PPR)** enabled via `cacheComponents: true` for faster page loads
- **Turbopack** enabled in development for 4-5x faster builds - **Turbopack** enabled in development for 4-5x faster builds
- **Static site generation** for all blog posts and pages - **Static site generation** for all blog posts and pages
- **Loading states** and error boundaries for better UX - **Loading states** and error boundaries for better UX
@@ -63,7 +62,7 @@ Configuration in `app/blog/[slug]/page.tsx`:
### Caching Strategy ### Caching Strategy
- **Static assets** cached for 1 year (`max-age=31536000, immutable`) - **Static assets** cached for 1 year (`max-age=31536000, immutable`)
- **PPR** caches static shells while streaming dynamic content - **Static site generation** for all pages (build-time prerendering)
- **Font optimization** with Next.js font loading - **Font optimization** with Next.js font loading
## Project Structure ## Project Structure

View File

@@ -8,8 +8,6 @@ const nextConfig = {
imageSizes: [16, 32, 48, 64, 96, 128, 256, 384], imageSizes: [16, 32, 48, 64, 96, 128, 256, 384],
}, },
// Enable Partial Prerendering (PPR) via cacheComponents in Next.js 16
cacheComponents: true,
// Compiler optimizations // Compiler optimizations
compiler: { compiler: {