Skip to main content
GoodFirstPicks
DashboardIssuesReposLeaderboard

GoodFirstPicks by Leaveitblank © 2026

CreatorRequest a RepoPrivacy PolicyTerms of Service
The link to Server Action's error with Client Component doesn't redirect to the corresponding section | GoodFirstPicks

The link to Server Action's error with Client Component doesn't redirect to the corresponding section

vercel/next.js 1 comments 1mo ago
View on GitHub
easyopenScope: clearSkill match: yesNext.jsTypeScriptReact

Why this is a good first issue

The issue involves fixing a broken documentation link in an error message.

AI Summary

The problem is a broken link in an error message that should redirect to a specific documentation section. The fix involves updating the link to point to the correct anchor. The maintainer comment suggests the documentation has been restructured, so the link needs to be verified and updated accordingly.

Issue Description

Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/condescending-shadow-lsly9n?workspaceId=ws_Sq4GMLXY8mhdG4GGt4EY7P

To Reproduce

  1. Start the application in development (next dev).
  2. Create a client component.
  3. Create a server action in a different file adding the "use server" directive to the top of the function body.
  4. Use the server action in the client component.
  5. Clicking on the "Read more" link from the error doesn't redirect to the corresponding client component section.

Current vs. Expected behavior

Once you get the error and you want to learn how to solve it, the link doesn't redirect to the client component section. Instead, it redirects you to the top of the page.

❌ Current link:

  • https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations#with-client-components

✅ Should be:

  • https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations#client-components

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
  Available memory (MB): 15714
  Available CPU cores: 16
Binaries:
  Node: 20.6.1
  npm: 10.9.2
  Yarn: 1.22.22
  pnpm: 9.15.0
Relevant Packages:
  next: 15.1.0 // Latest available version is detected (15.1.0).
  eslint-config-next: 15.1.0
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Developer Experience

Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

Additional context

No response

GitHub Labels

bug

Want to work on this?

Claim this issue to let others know you're working on it. You'll earn 5 points when you complete it!

Risk Flags

  • documentation link may have changed
Loading labels...

Details

Points5 pts
Difficultyeasy
Scopeclear
Skill Matchyes
Test Focusedno