From 7964772f82cc182bbe45be855150d227eceed796 Mon Sep 17 00:00:00 2001 From: Anton Nikolaev Date: Tue, 28 Jan 2020 06:12:40 -0800 Subject: [PATCH] Added information about pre-requisite for debugging in VSCode Summary: Added information that "Debugger for Chrome" extension is required to be able to debug in VSCode. Reviewed By: passy Differential Revision: D19599117 fbshipit-source-id: 7323fb59daae24fe6b914e9ddb450326b135ad2b --- docs/extending/debugging.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/extending/debugging.md b/docs/extending/debugging.md index 6f00c500c..843c678ad 100644 --- a/docs/extending/debugging.md +++ b/docs/extending/debugging.md @@ -21,7 +21,7 @@ To attach the running Flipper instance open new tab in Google Chrome, navigate t ## Visual Studio Code -If you prefer to use the same editor for both coding and debugging, you can attach to the running Flipper instance for debugging right from Visual Studio Code. To do this, start Flipper in development mode (`yarn start`), select `Debug and Run` tab in VSCode, and run task `Attach to Running Renderer`. By default this task is set as the first one,so you can just press `F5` to run it. +If you prefer to use the same editor for both coding and debugging, you can attach to the running Flipper instance for debugging right from Visual Studio Code. First of all, you need to install extension "Debugger for Chrome". Then, to start debugging, launch Flipper in development mode (`yarn start`), select `Debug and Run` tab in VSCode, and run task `Attach to Running Renderer`. By default this task is set as the first one, so you can just press `F5` to run it. ![Attach From Visual Studio Code](/docs/assets/debugging-from-vscode.png)