Skip to content

Conversation

stephan-noel
Copy link

Fixes #8089

Before inside the "Optimizing performance" deep dive, the link with text "Performance" would send us to the legacy React docs.

image

Clicking on "Performance" above would send us here:

image

The link on this legacy page for "memo: Skipping re-rendering when props are unchanged" points to the new docs. This is the same link used in this PR.

Now clicking on "Performance" navigates to here:

image

Additional Considerations

Despite the old docs linking to https://react.dev/reference/react/memo#skipping-re-rendering-when-props-are-unchanged, this new page is in the Reference section for memo. There doesn't seem to be a comprehensive Learn section for performance.

The closest I could find is https://react.dev/learn/react-compiler/introduction#optimizing-re-renders, which may be more appropriate considering the React Compiler is now stable. https://react.dev/reference/react/memo#skipping-re-rendering-when-props-are-unchanged still does mention the React Compiler, though only does so later down.

Topics in legacy link that are not covered in the new link

  • Using the production build
  • Profiling (probably needs an update with the release of the new Profiler Panel)
  • Virtualization (mentioning Activity is probably related)

Topics not mentioned in either related to reducing the frequency of re-renders

"Lift content up"

@github-actions
Copy link

github-actions bot commented Oct 22, 2025

Size changes

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

@moijes12
Copy link
Contributor

@stephan-noel I agree with the points mentioned by you in the Additional Considerations in your comment above.

Use relative link

Co-authored-by: Radoš Milićev <40705899+rammba@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Typo]: Optimizing performance points to old docs

3 participants