From 8f8736b05610f1b014620b47af92a2e2faa545b4 Mon Sep 17 00:00:00 2001 From: Aviv Keller Date: Mon, 24 Nov 2025 16:49:04 -0500 Subject: [PATCH] fix(formatting): don't indent code block Updated code block formatting for clarity. Signed-off-by: Aviv Keller --- apps/site/pages/en/learn/diagnostics/flame-graphs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/apps/site/pages/en/learn/diagnostics/flame-graphs.md b/apps/site/pages/en/learn/diagnostics/flame-graphs.md index 5ebdd3062bd9c..53245fef7cb35 100644 --- a/apps/site/pages/en/learn/diagnostics/flame-graphs.md +++ b/apps/site/pages/en/learn/diagnostics/flame-graphs.md @@ -34,9 +34,9 @@ Now let's get to work. 2. Try running `perf` - it might complain about missing kernel modules, install them too 3. Run node with perf enabled (see [perf output issues](#perf-output-issues) for tips specific to Node.js versions) - ``` - perf record -e cycles:u -g -- node --perf-basic-prof --interpreted-frames-native-stack app.js - ``` +```bash +perf record -e cycles:u -g -- node --perf-basic-prof --interpreted-frames-native-stack app.js +``` 4. Disregard warnings unless they're saying you can't run perf due to missing packages; you may get some warnings about not being able to access kernel module samples which you're not after anyway. 5. Run `perf script > perfs.out` to generate the data file you'll visualize in a moment. It's useful to [apply some cleanup](#filtering-out-nodejs-internal-functions) for a more readable graph