How Debug Nodejs backend part with VSCODE

Retired Boards Appdev Partners Discussion
1

Hi

I have follow the link How Debug React shopify app , for the front-end part and it work right.

However when i try to debug the backend part nodejs, the breakpoint remain “Unbound Breakpoint”.

How i can resolve it ?

Thanks you

2

Hello there

Debugging a Node.js backend with Visual Studio Code (VSCode) is a straightforward process. Here are the steps to follow:

  1. Open your Node.js backend project in VSCode.
  2. Click on the “Debug” tab in the left sidebar, or press the F5 key to open the debugger.
  3. Click on the “Create a launch.json file” button, or press the “Add Configuration” button in the top right corner of the debugger. This will open the “Add Configuration” dialog.
  4. In the “Add Configuration” dialog, select “Node.js” from the list of options. This will create a new launch configuration for your Node.js project.
  5. In the launch configuration, you can specify the entry point for your application (e.g., server.js) and any other configuration options you want to set (e.g., environment variables, command line arguments, etc.).
  6. Once you have your launch configuration set up, you can start debugging by clicking on the green “Start Debugging” button in the debugger, or by pressing the F5 key again. This will launch your application in debug mode.
  7. You can then set breakpoints in your code by clicking on the left margin of the code editor, or by pressing the F9 key while the cursor is on a line of code. When the application hits a breakpoint, it will pause execution and allow you to inspect the state of the application.
  8. You can use the debugger controls (e.g., “Continue,” “Step Over,” “Step Into,” etc.) to navigate through your code and debug it line by line.

I hope this helps!

3

An “unbound breakpoint” is a breakpoint that has been set in your code, but that cannot be hit when the code is executed. This can occur for several reasons:

  1. The code containing the breakpoint has not been loaded: If the code containing the breakpoint has not been loaded (e.g., it is part of a module that has not yet been imported), the breakpoint will remain unbound until the code is loaded.
  2. The code has been deleted or moved: If the code containing the breakpoint has been deleted or moved, the breakpoint will remain unbound because the debugger will not be able to find the code to stop at.
  3. There is a syntax error in the code: If there is a syntax error in the code, the debugger may not be able to bind the breakpoint because it cannot parse the code.

To fix an unbound breakpoint, you will need to address the underlying cause of the problem. For example, you may need to import a missing module, fix a syntax error, or update the location of a moved file. Once the issue has been resolved, the breakpoint should become bound and be hit when the code is executed.