docs: scaffold docs structure for Performance tracks #7938
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Size changes📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
7ba84af to
b59f74c
Compare
ee8df3b to
663e97f
Compare
663e97f to
499511f
Compare
499511f to
5f43f3f
Compare
rubennorte
reviewed
Sep 11, 2025
| @@ -0,0 +1,129 @@ | |||
| --- | |||
| title: React Performance tracks | |||
There was a problem hiding this comment.
Suggested change
| title: React Performance tracks | |
| title: React performance tracks |
It feels weird to capitalize performance. I'd either capitalize everything or just React. There are other examples of this in the doc.
rubennorte
reviewed
Sep 11, 2025
|
|
||
| </Intro> | ||
|
|
||
| These tracks are designed to provide developers with comprehensive insights into their React application's performance by visualizing React-specific events and metrics alongside other critical data sources such as Network requests, JavaScript execution, and Event Loop activity, all synchronized on a unified timeline within the Performance panel for a complete understanding of application behavior. |
There was a problem hiding this comment.
Suggested change
| These tracks are designed to provide developers with comprehensive insights into their React application's performance by visualizing React-specific events and metrics alongside other critical data sources such as Network requests, JavaScript execution, and Event Loop activity, all synchronized on a unified timeline within the Performance panel for a complete understanding of application behavior. | |
| These tracks are designed to provide developers with comprehensive insights into their React application's performance by visualizing React-specific events and metrics alongside other critical data sources such as network requests, JavaScript execution, and event loop activity, all synchronized on a unified timeline within the Performance panel for a complete understanding of application behavior. |
rubennorte
reviewed
Sep 11, 2025
|
|
||
| ### Components {/*components*/} | ||
|
|
||
| The Components track visualizes the durations of React components. They are displayed as a flamegraph, where each entry represents the duration of the corresponding component render and all its descendant children components. |
There was a problem hiding this comment.
We should mention that not all components rendered are shown here. Only the ones taking more than a specific amount of time.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Work in progress. Screenshots are not final.