This capability is absolutely critical for bug fixing. To be able to traverse the path of server-side requests in real-time, and see the data that is flowing and being used in conditional logic would rapidly speed up the time in finding and fixing bugs.
My current Wappler debugging process involves trying to parse the log output with the Debug flag set to true, and inserting the equivalent of multiple print() statements directly into my server-side end-points (which then need to be removed later).
With the help of @JonL , I was able to connect the Chrome debugger to the Node.js server running my Wappler project, but debugging the server-side JavaScript that underpins a Wappler project proved to be just too granular. I really need it at the same level as the Wappler API editor, with a focus on the data that's available in that workflow (e.g. HTTP parameters, session variables, local and global variables).