From 17fd59914627f16a5c140c8044e292321b417575 Mon Sep 17 00:00:00 2001 From: Kunall Banerjee Date: Tue, 19 Aug 2025 22:51:01 -0400 Subject: [PATCH] fix(docs): remove redundant section describing caveats of profiling --- src/content/reference/react/Profiler.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/src/content/reference/react/Profiler.md b/src/content/reference/react/Profiler.md index 188b2d1b2bd..10b2db2d31c 100644 --- a/src/content/reference/react/Profiler.md +++ b/src/content/reference/react/Profiler.md @@ -35,10 +35,6 @@ Wrap a component tree in a `` to measure its rendering performance. * `id`: A string identifying the part of the UI you are measuring. * `onRender`: An [`onRender` callback](#onrender-callback) that React calls every time components within the profiled tree update. It receives information about what was rendered and how much time it took. -#### 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) - --- ### `onRender` callback {/*onrender-callback*/} @@ -129,4 +125,3 @@ You can also nest `` components: Although `` is a lightweight component, it should be used only when necessary. Each use adds some CPU and memory overhead to an application. --- -