From 035e07e3be0f338cf8f00a0ee082f2387eb608e5 Mon Sep 17 00:00:00 2001 From: Matthieu Riegler Date: Mon, 17 Nov 2025 10:12:07 +0100 Subject: [PATCH] refactor(core): promote the custom track profiler to stable. We didn't get much report on the feature itself so we feel confident about promoting it to stable. In parallel we'll also land #62959 but one is not blocking the other. fixes #64996 (cherry picked from commit c15836c8c75c0532388cccee2007099e06ff6ea9) --- packages/core/src/render3/debug/chrome_dev_tools_performance.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/core/src/render3/debug/chrome_dev_tools_performance.ts b/packages/core/src/render3/debug/chrome_dev_tools_performance.ts index 7b72292a1bc..52e6fce9ce6 100644 --- a/packages/core/src/render3/debug/chrome_dev_tools_performance.ts +++ b/packages/core/src/render3/debug/chrome_dev_tools_performance.ts @@ -228,7 +228,7 @@ function getProviderTokenMeasureName(token: any) { * * Note: integration is enabled in the development mode only, this operation is noop in the production mode. * - * @experimental + * @publicApi v21.0 * * @returns a function that can be invoked to stop sending profiling data. * @see [Profiling with the Chrome DevTools](best-practices/profiling-with-chrome-devtools#recording-a-profile)