Document React's profiling builds #8054
Merged
+15
−5
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
eps1lon
commented
Oct 5, 2025
|
|
||
| #### Caveats {/*caveats*/} | ||
|
|
||
| * Profiling adds some additional overhead, so **it is disabled in the production build by default.** To opt into production profiling, you need to enable a [special production build with profiling enabled.](https://fb.me/react-profiling) |
There was a problem hiding this comment.
That gist included docs for Webpack 4 and CRA 3. Both are either outdated or deprecated so I just kept a vague ("use bundler aliases or framework").
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! 🙌 |
eps1lon
force-pushed
the
sebbie/10-06-document_react_s_profiling_build
branch
from
c7c2d22 to
7f93de1
Compare
hoxyq
approved these changes
Oct 6, 2025
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.
Preview: https://react-hyygbakob-fbopensource.vercel.app/reference/dev-tools/react-performance-tracks
Only documents that they exist and when you need them. Specifics are build tool and framework dependent. We could come up with a list of build tools/frameworks we want to reference but how that list is chose and curated may be controversial so I left it vague for now.
The main motivation was that the perf track docs said you only need to use
<Profiler>in prod builds to opt-into Component tracks. But you need both: a profiling build and wrapping a subtree in<Profiler>/RDT installed.