visual studio code node js attach to chrome

VISUAL STUDIO CODE NODE JS ATTACH TO CHROME HOW TO

The CLI debugger is an uncomfortable solution directly after debugging with console.log. You start an interactive debugging shell.Īnd you open a TCP connection on port 5858 where you can connect a remote debugger with your application. If you start your application on the command line with node debug index.js where index.js is the starting point of your application, then it is started in debug mode. Node.js ships with a built-in debugging facility. In particular, they let you pause the execution of your application at specific points in the code and inspect and modify the values of the variables while the program is still running. Also, trying to log out variables alongside the noise of other potential logging operations may make debugging difficult when you're attempting to find the values you are debugging.ĭebugging tools provide you with a few important functionalities that console.log isn’t able to provide. Besides slowing down the development of your app, it also makes your writing dirty and creates unnecessary code. Using console.log to debug your code generally sends you into an infinite loop of stopping your app, adding a console.log, and starting your app again. But why? The answer is easy: It’s inconvenient to use the debugger if you haven’t set up your environment correctly.

VISUAL STUDIO CODE NODE JS ATTACH TO CHROME HOW TO

This post describes how to efficiently debug Node.js programs using the latest Google Chrome DevTools.Ī lot of developers use console.log in order to debug their application. Debugging is the task of identifying and removing errors from software applications, and it's more than just printing out values in your code.

Visual studio code node js attach to chrome