Skip to main content


This section on Redwood applications debugging is organized as a set of three chapters. All the information presented in this document extends the sections Debugger information from the RedwoodJS tutorial application.

We are describing the concept of debugging RedwoodJS applications using two different tools (Chrome and VSCode debuggers), skipping several alternatives. We will also skip the use of Chrome in a distributed setup, meaning that we will consider only the case of debugging the front end of the RedwoodJS application. The next two cases, A and B briefly describe our intent

Case A: Using Chrome debugger

The simplest use case scenario is to start the target application from the Terminal (use the command yarn rw dev). This results with

Image 1 - running `yarn rw dev` in the terminal (shown on the left)

Please check the section Setup the Chrome debugger for details explaining the final debugging configuration shown below:

Image 2 - Chrome debugger based configuration

Case B: Using VSCode debugger

The difference between case A (debugging with Chrome Devtools debugger) and using VSCode debugger is in the means of using Chrome in such debugging session. This is the workflow to be used:

  1. Start the VSCode from the terminal via vscode . command, making sure to first set the current directory to the folder that contains you project's parts (In my case)