Skip to content

fix(docs): update broken dynamic rendering link across codebase (#80696) #80781

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

Open
wants to merge 1 commit into
base: canary
Choose a base branch
from

Conversation

ibrahimmemonn
Copy link

What?

Replaced 33 instances of the outdated dynamic rendering docs link with the updated working link.

Old:
https://nextjs.org/docs/app/building-your-application/rendering/static-and-dynamic#dynamic-rendering

New:
https://nextjs.org/docs/app/building-your-application/rendering#dynamic-rendering

Why?

The old link returns a 404 and is shown in error messages when using certain features like revalidatePath(). This leads to a confusing developer experience (DX), especially for new users trying to understand rendering behavior.

How?

  • Searched the codebase for the broken URL.
  • Replaced it in 33 instances across 13 files.
  • Verified the new URL points to the correct docs section.
  • Ensured consistency across all updated files.

Checklist


This PR improves developer experience by ensuring users are pointed to the correct documentation during runtime errors.

…el#80696)

Replaced 33 instances of the outdated dynamic rendering docs link with
the updated and working link:
Old: https://nextjs.org/docs/app/building-your-application/rendering/static-and-dynamic#dynamic-rendering
New: https://nextjs.org/docs/app/building-your-application/rendering#dynamic-rendering

This fixes broken links in dev error messages and improves DX.
@ijjk ijjk added tests Turbopack Related to Turbopack with Next.js. type: next labels Jun 23, 2025
@ijjk
Copy link
Member

ijjk commented Jun 23, 2025

Allow CI Workflow Run

  • approve CI run for commit: b4c0109

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

@ibrahimmemonn
Copy link
Author

Allow CI Workflow Run

  • approve CI run for commit: b4c0109

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

Thanks! Let me know if there’s anything you'd like me to change 🙌

Copy link

codspeed-hq bot commented Jun 23, 2025

CodSpeed Performance Report

Merging #80781 will not alter performance

Comparing ibrahimmemonn:fix-broken-doc-link (b4c0109) with canary (e231928)

Summary

✅ 3 untouched benchmarks
⁉️ 9 dropped benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

Benchmark BASE HEAD Change
⁉️ build[date-fns-all] 2.8 s N/A N/A
⁉️ build[date-fns-single] 1.6 s N/A N/A
⁉️ build[framer-motion-all] 3.9 s N/A N/A
⁉️ build[framer-motion-single] 2.7 s N/A N/A
⁉️ build[joy] 2.5 s N/A N/A
⁉️ build[lucide-react-all] 12.4 s N/A N/A
⁉️ build[lucide-react-single] 1 s N/A N/A
⁉️ build[mui] 3.9 s N/A N/A
⁉️ build[shiki] 6.3 s N/A N/A

@ibrahimmemonn
Copy link
Author

CodSpeed Performance Report

Merging #80781 will not alter performance

Comparing ibrahimmemonn:fix-broken-doc-link (b4c0109) with canary (e231928)

Summary

✅ 3 untouched benchmarks ⁉️ 9 dropped benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

Benchmark BASE HEAD Change
⁉️ build[date-fns-all] 2.8 s N/A N/A
⁉️ build[date-fns-single] 1.6 s N/A N/A
⁉️ build[framer-motion-all] 3.9 s N/A N/A
⁉️ build[framer-motion-single] 2.7 s N/A N/A
⁉️ build[joy] 2.5 s N/A N/A
⁉️ build[lucide-react-all] 12.4 s N/A N/A
⁉️ build[lucide-react-single] 1 s N/A N/A
⁉️ build[mui] 3.9 s N/A N/A
⁉️ build[shiki] 6.3 s N/A N/A

Thanks for the CodSpeed report! Since this PR only updates documentation links and doesn't touch runtime or build code, the dropped benchmarks should be safe to ignore. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests Turbopack Related to Turbopack with Next.js. type: next
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Docs: not found docs link from dev server
2 participants