Select “Debug: Create JavaScript Debug Terminal” from the menu.Select which process you want to attach the debugger to.Īdding a JavaScript debug terminal is quick and painless and a great option if you want to do broad or general bug fixing. From here, you will see all of the processes that can be debugged by the Node.js debugger.Select “Attach to Node Process” from the menu.Open the command palette by pressing “Ctrl+Shift+P” on your keyboard.To attach the debugger to a Node.js process, do the following: This requires a bit more work but it will save you time if you know exactly which process is causing problems. You can attach your Node.js debugger to processes manually as well.

To enable Auto Attach, follow these steps: Auto AttachĪuto attach is a feature that will automatically attach the Node debugger to certain Node.js processes in VSCode’s terminal. You aren’t building anything from scratch, but using previously made code to debug. “Attach” configurations, on the other hand, involve you attaching a configuration from outside VSCode while the program in VSCode is running. Launch configurations mean that you, the coder, are writing the code or “recipe” for your debugging session. Here’s a short breakdown of the methodology for each mode.įirst, let’s discuss “launch” configurations. VSCode has two modes of debugging – “launch” and “attach.” Each mode has its own pros and cons and each is suited to a certain kind of coder. Inside the IntelliSense configuration array, choose to add another configuration.Bring up IntelliSense (Shift+Space) to bring up the menu, then select “Add configuration.”.

In the “Run” menu, select “Add configuration.”.

Luckily, you can add new configurations to the debugger. With particularly tough bugs, there’s a chance that the database you have on VSCode doesn’t have the configuration you need.

You can also access the debugger menu by first accessing the Command Palette by pressing “Ctrl+Shift+P”.

Select “Launch Program.” Once you’ve selected it, press F5 to start the debugger.

In the Run view of VSCode, find “Configuration dropdown.”.

To run the debugger, we will first need to select our launch configuration. Now that all of the preparation is done, we can start our debugging session.

To check the debugger’s attributes, press “Ctrl+Space”.

Check under your folder “hello.” There should be a tab called “.vscode” and the launch.json should be in that tab.

Go back to the File Explorer by pressing “Ctrl+Shift+E.”.

VSCode will automatically select the debug environment, but if it doesn’t detect anything, select “Node.js.”.

In the “Run view” menu, select “create a launch.js.”.

Note that you’ll need to have this program before you can finally run the debugger. For the purposes of this guide, select the “create a launch.js” option.

A menu will appear with three options.

You can also quickly access it by pressing “Ctrl+Shift+D” on your keyboard.

On the sidebar of VSCode, select the “Run” icon.

It also includes a taskbar where you can configure settings and debugging commands.

When you first start, you’ll need to familiarize yourself with the all of the information the debugger has for you. Run Viewįrom here, you’ll be able to utilize all of VSCode’s debugging features. The output will say “Hello, World.”Ĭongratulations, you’ve written your first program and are now ready to run VSCode’s debugger.

Save the file by pressing “Ctrl +S” on the keyboard.

In the console command, type the following code:.

Your file should show up with the name “Hello.” Click the “New File” button on the right side of the file name.

Open VSCode and in the command prompt, type the following code:.

Create an empty folder on your Desktop and name it “hello.”.

The version of Node.js you installed should appear.

To see if Node.js is installed, create a new terminal and type “node-version” in the terminal.

Before you begin, make sure you have Node.js downloaded and installed on your computer.

Visual studio code debug android device