In the preceding screenshots, both with VSC and Chrome, I opened the out/restful_regions.js file and set a breakpoint at the place where a SELECT is done in order to get some regions. Doing a request for /regions/uy caused the run to pause at the point. You can then do the following:

• Examine all variables, including block, local, and global ones—this includes the possibility of modifying their values, if you want to
• Add some variables or expressions to watch; whenever execution pauses, you'll see their values
• See the call stack
• Set some specific breakpoints

As for program execution, you can do the following:

• Stop execution at any breakpoint
• Restart execution
• Step through your code, with the option of drilling down to analyze function calls

If you use Chrome, you'll be able to get some extra options, like memory usage analysis or code execution profiling, but clearly the web-specific options won't do any good. However, debugging your code by using the inspection option is a very good aid for bug chasing, so get used to it; you'll appreciate it a lot!